History Helps - Cycle-Over-Cycle Bug Analysis and Recommendations for Test Improvement
Source: Adobe Systems
The IT industry is witnessing projects become increasingly large and complicated. On the other hand, release and go-to-market timelines are shrinking day by day. These complexities, coupled with resource turnover in projects, presents quality managers with challenges of epic proportions. Within a shrinking testing cycle, test managers strive hard to maintain testing processes and discover as many valid bugs as possible early in the cycle. A strategic approach for formulating robust test plans and testing strategies is to conduct a retrospective analysis of all historical bugs and bugs logged during last cycle of the project, and identify high bug penetration areas, components, and modules. Analysis of historical bugs also helps to identify areas where the efficiencies of the testing team needs improvement.