Tuesday, June 14, 2016

Identify test plan availability for each bug

It was a good practice followed by QA in the company I worked before.

It is enforced by the QA manager but also known by several Dev Managers.  It is for close loop analysis.


For each customer bug, to prevent the problem happen again, the QA manager need to analyze the bugs and flag the bug.

1. Test Plan Available
If a test case exists, the QA manager mark the bug with this status.

2. Test Plan is Not Available but Feasible
A QA engineer will be assigned to work on creating the test case.
Once the test case is completed, set the status back to #1.

3. Test Plan is Not Available but Not Feasible
Either this is not a commonly seen issue or an issue that is not due to a defect in the product.
This is the end of the evaluation of the customer bugs from QA's perspectives.


Post a Comment