Bug's Story ()
-
date post
20-Oct-2014 -
Category
Business
-
view
3.643 -
download
0
description
Transcript of Bug's Story ()
![Page 2: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/2.jpg)
Now Flashback……
Scene 0: Bugs are all dead
![Page 3: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/3.jpg)
Scene 1: Requirements
Bug X comes into this world……
![Page 4: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/4.jpg)
Scene 2: Design
Bug Y & Z also follow referred by Mr. X……
![Page 5: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/5.jpg)
Scene 3: Coding
Looks like whole family is joining the business……
![Page 6: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/6.jpg)
Scene 4: Bug’s celebrating
Someone is celebrating success…
![Page 7: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/7.jpg)
Scene 5: Testing
Hero makes an entry
![Page 8: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/8.jpg)
Scene 6: Manager’s Reaction
![Page 9: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/9.jpg)
Scene 7: Devs Reaction on Fixing
![Page 10: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/10.jpg)
Scene 8:Retesting
Hero in action …
![Page 11: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/11.jpg)
Scene 9: Back to the future
Mission Completed
![Page 12: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/12.jpg)
Scene 10: Bugs are dead
![Page 13: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/13.jpg)
Scene 11:Somebody is partying
Now it is testing team’s turn… but stop ! We got a twist
![Page 14: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/14.jpg)
Scene 12:End User
Oops. Did we miss someone ? Yeah we did.
![Page 15: Bug's Story ()](https://reader033.fdocuments.in/reader033/viewer/2022061106/54453bdaafaf9f18098b45aa/html5/thumbnails/15.jpg)
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