Software defect reports are among the most important deliverables to come out of software testing. They are as important as the test plan and will have more impact on the quality of the product than most other deliverables from the software test team. It's worth the effort to learn how to write an effective defect report that conveys the proper message and simplifies the process for everyone.
When the design and the coding are complete, and the product seems ready to ship, it’s hard to understand why testing takes so long. Discover how your source code management system can help you unblock the testing bottleneck.
What's your take on the defect-tracking debate? Are defect logs helpful repositories of knowledge or cumbersome, inefficient inventories? Lisa Crispin took to the trenches to find out how different industry workers view defect-tracking systems. Find out what they had to say.
Users don't have to be doomed to the nightmare of software fraught with defects that should have been fixed before release. Time spent testing now can save you from the Death Spiral later. Remember: If you don't have time to do it right, how will you have time to do it over . . . and over . . . and over?
Need information but don’t have time to wade through bookracks looking for that perfect reference? The StickyMinds.com Books Guide can help. Get the scoop from StickyMinds.com members on three books that can keep you up to date on the latest issues.