Add a list with Rejection Reasons to your bugs.

A PractiTest customer was telling me about a problem they have with people not writing down their reasons when rejecting a bug, or writing unclear explanations in the Description or Comments fields.

I know exactly what she meant…  I also hate this issue plus the fact that since the data is in Free Text it is very difficult to track the reasons and keep statistics (in case you believe like I do in tracking this behavior as part of an on-going improvement policy).

My solution is simple: I create a customized field called Reject Reason with the acceptable values for rejecting bugs in the project.  Usually these values are: Not a Bug, Not Clear, Unable to Reproduce, and Duplicate.

I find that by providing a list instead of asking my users to write down their explanation in free text they are more willing to comply.

Also since I have this as a structured list, PractiTest provides me automatically with statistics to keep track of my rejections and make corrections if needed.

About PractiTest

Practitest is an end-to-end test management tool, that gives you control of the entire testing process - from manual testing to automated testing and CI.

Designed for testers by testers, PractiTest can be customized to your team's ever-changing needs.

With fast professional and methodological support, you can make the most of your time and release products quickly and successfully to meet your user’s needs.

2 Responses to Add a list with Rejection Reasons to your bugs.

  1. Martin March 15, 2011 at 1:44 pm #

    I agree with you Joel, but I would go even further and would add a more specific description in the “not a bug” value. This is because many times I found the DEV team flagging several bugs with this status and QA can't be sure about what where the parameters they took into consideration to determine that the issue is actually not a bug. To get it straight, they usually flag an issue with this status when they do not want to fix it.

    Regards.

  2. joelmonte March 18, 2011 at 7:35 am #

    Hi Martin,

    I totally agree, on some occasions I've asked developers to add a comment with the rejection reason since a drop-down list may be insufficient.

    -joel

Leave a Reply

shares