To Test or Not to Test?
0 likes331 views
The document appears to be a report analyzing the reopening rate of issues over 7 versions of a software project. It includes graphs showing the reopening rate decreased from 20% in version 1 to under 5% in version 7. It also discusses cost savings of $200,000 from reducing reopens. Additionally, it examines the types of issues found during testing versus after release, with rare configuration errors typically only found after release.
To Test or Not to Test?
- 1. Amos Uzan
- 2. 2
- 3. 20% 20% 3
- 4. 4
- 5. 25% 25% 20% 20% % ReOpen 15% 15% 10% 10% 5% 0% Ver 1 ver 2 Ver 3 Ver 4 Ver 5 Ver 6 Ver 7 Versions 5
- 6. 6
- 7. 7
- 8. ~200,000$ 200,000$ 8
- 9. 9
- 10. 120 100 80 60 Open Fixed 40 20 0 Ver 1 ver 2 Ver 3 Ver 4 Ver 5 Ver 6 Ver 7 10
- 11. 11
- 12. Version 5, 6, 7 12
- 13. Version 5, 6, 7 13
- 14. 14
- 15. Cannot be found in the QA Cycle Represent a specific configuration Rare scenario Can be found in the QA Cycle (severity 3 & 4) 15
- 16. 16
- 17. 17
- 18. 18
- 19. 19
- 20. 20
- 21. 21
- 22. 22
- 23. 23
- 24. 24