Convincing your PM to let you fix bugs
•Download as PPTX, PDF•
0 likes•464 views
How does integration (or functional) testing help improve confidence in software quality.
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Convincing your PM to let you fix bugs
Similar to Convincing your PM to let you fix bugs (20)
Recently uploaded
Recently uploaded (20)
Convincing your PM to let you fix bugs
- 1. Convincing your PM to let you fix bugs Garret Fick
- 2. 19 April 2012 Discovered code I wrote caused customer crash
- 3. This isn’t about timeline ??/??/2011 Many tests failing ??/??/2011 Crash introduced, many tests still failing 29/12/2011 “Testing-only bug” fixed 12/02/2012 Product released with crash 19/04/2012 WinQual (crash reports) show bug 29/09/2012 Included in service pack
- 4. Objective • Convince the value of integration tests • Share my best practices • Not teach you how to write integration tests
- 5. LACK OF CONFIDENCE Where did it go?
- 6. What you need to know
- 7. What you need to know Automated tests were failing
- 8. What you need to know A fix was found
- 9. The fix was a one-line fix
- 10. Fix not included in the release
- 11. We were okay to exclude because… • We didn’t know it would crash • We didn’t feel confident to fix
- 12. NOT CONFIDENT? IT IS YOUR CODE!
- 13. Testing and quality Confidence Unit System
- 14. Confidence gap Unknown coverage gives a confidence gap External quality Confidence Internal quality Unit Integration System
- 15. A confidence gap means… Fix not included in the release
- 16. Fixing the confidence gap may mean… Fix included in the release
- 17. USING INTEGRATION TESTS To fill the confidence gap
- 18. Integration tests… • Small-ish modules of code • Black box tests • Cross boundaries • Probably use common utilities • May use mocks
- 19. Benefits • Increase confidence • Increase test coverage • Fast to write (leverage unit tests setup) • Accelerate development (no UI) Risks • Duplication • Maintainability
- 20. LAST REMARKS
- 21. 19 April 2012 Don’t let it happen to you
- 22. Don’t be afraid - test • Tests increase confidence – Unit for coverage – Integration for interactions – System for regressions
Editor's Notes
- 19 April, 2012. The truth was revealed. Code that I wrote caused customer crash. Disbelief -> How could I understand, write, modify and test code, and still crash? How slip through months of testing? Investigation -> Fix
- You’ve see that talk before.
- We fixed a bug that “only happened in our auto-test system”
- We fixed a bug that “only happened in our auto-test system”
- We fixed a bug that “only happened in our auto-test system”
- This is a pretty common situation.
- http://blogs.studentlife.utoronto.ca/lifeatuoft/files/2012/10/shock1.jpg
- You need something that tells you a bit about the external quality and a bit about the internal quality Because you are limited in what you can test with end-to-end testing From Growing object-oriented software, guided by tests
- You need something that tells you a bit about the external quality and a bit about the internal quality Because you are limited in what you can test with end-to-end testing From Growing object-oriented software, guided by tests
- We fixed a bug that “only happened in our auto-test system”
- We fixed a bug that “only happened in our auto-test system”