|
Use the Rejected Defect Ratio to Improve Bug Reporting There are many metrics to measure the effectiveness of a testing team. One is the rejected defect ratio, or the number of rejected bug reports divided by the total submitted bug reports. You may think you want zero rejected bugs, but there are several reasons that’s not the case. Let's look at types of rejected bugs, see how they contribute to the rejected defect ratio, and explore the right ratio for your team.
|
|
|
Building Better Bug Reports Each bug report is colored by the judgment of the person producing it. Testers should want to develop their skills to be better communicators with bug backlog stakeholders so that an issue can be solved in a way that benefits everyone. Read on to challenge your ideas of what builds a clear, concise, contextualized—but still courteous—bug report.
|
|
|
The Why, When, and How of Defect Advocacy When Ipsita Chatterjee started testing about a decade ago, her test manager and mentor told her, "A good tester is not one who finds the most defects, but one who closes the most defects." After years of developing her testing and test management skills, she couldn't agree more. She now asks herself, how can a tester close more defects? Her answer: by using a fine combination of product and technical knowledge, intuition, and personal skills. With that in mind, this article focuses on the definition of defect advocacy; why, when, and how to approach it; and a few ways of achieving it to an optimum level, which should help you release quality software applications.
|
|
|
After the Bug Report We crank out bug reports and expect them to return like a boomerang so we can check to see if the bugs were fixed. In this week's column, Danny Faught shares some ideas drawn from recent experiences that could make you a better customer advocate subsequent to filing a bug report.
|
|