STAREAST 2002: Writing Better Defect Reports

Kelly Whitmill, IBM

Why is it some testers get a better response from developers than others? Part of the answer lies in their defect reports. But following a few simple guidelines can smooth the way for a much more productive environment. That's because the objective shouldn't be to write the perfect defect report, but to write an effective defect report that conveys the proper message, gets the job done, and simplifies the process for everyone. It's important that you use this report to ask and answer the right questions. Kelly Whitmill gives you a quick mental inspection checklist you can reference each time you write a defect report. You'll walk away with information that can make a significant difference the day you get back to work, on a topic that's often overlooked in the industry.

Upcoming Events

Sep 22
Oct 13
Apr 27