Many software organizations have mature defect tracking processes and tooling. Defect reports are often the primary means by which testers and developers communicate, and many teams run their development priorities from the defect tracking system. Bad news. We now find ourselves swimming in defect reports, the majority of which are irrelevant, out of date, repeated, not reproducible, and difficult to associate to the features we've committed to deliver. The solution is to adopt techniques that pull testing forward in the software lifecycle so we replace most of the defect reports with "failing" test cases that are transitory in nature, easily reproduced, and require little management
overhead. The result is that we dramatically reduce our defect management burden, improve our responsiveness to customer feature requests, and ship with higher software quality.
- Typical defect reporting cycles in test-last development environments
- Reduce defect reports and their management burden with early test development
- The gains in productivity and quality achieved by real-world teams