Bug’s Story Written by a unknown Tester [email_address] (Reference :- From My Dear friend RAJ)
Now Flashback…… Scene 0: Bugs are all dead
Scene 1: Requirements Bug X comes into this world……
Bug Y & Z also follow referred by Mr. X…… Scene 2: Design
Looks like whole family is joining the business…… Scene 3: Coding
Someone is celebrating success… Scene 4: Bug’s celebrating
Hero makes an entry Scene 5: Testing
Scene 6: Manager’s Reaction
Scene 7: Devs Reaction on Fixing
Hero in action … Scene 8:Retesting
Mission Completed Scene 9: Back to the future
Scene 10: Bugs are dead
Now it is testing team’s turn… but stop ! We got a twist Scene 11:Somebody is partying
Oops. Did we miss someone ? Yeah we did. Scene 12:End User
Testing team should find bugs as and when they come up e.g. Requirements, Design, Coding. This will ensure that team cost of fixing these bugs will be much lower Team and end users won’t be surprised with some creepy bugs Retesting is not enough, Regression is always important Story Over: Key Learning's
0 comments
Post a comment