Bug’s Story

Written by a unknown Testerraj.kamal13@gmail.com

www.itest.co.nr

Now Flashback……

Scene 0: Bugs are all dead

Scene 1: Requirements

Bug X comes into this world……

Scene 2: Design

Bug Y & Z also follow referred by Mr. X……

Scene 3: Coding

Looks like whole family is joining the business……

Scene 4: Bug’s celebrating

Someone is celebrating success…

Scene 5: Testing

Hero makes an entry

Scene 6: Manager’s Reaction

Scene 7: Devs Reaction on Fixing

Scene 8:Retesting

Hero in action …

Scene 9: Back to the future

Mission Completed

Scene 10: Bugs are dead

Scene 11:Somebody is partying

Now it is testing team’s turn… but stop ! We got a twist

Scene 12:End User

Oops. Did we miss someone ? Yeah we did.

Story Over: Key Learning's

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

Thank you Contact: raj.kamal13@gmail.com