Can I manage defect validation process in Testuff?
Yes you can. Here’s a possible process you may want to follow:
- Defects are usually reported while executing tests, sometimes a defect report can be reported as is, not related to any test. In both cases, you end up with a group of approved defects, designated for fixing.
- The defects are assigned for fixing. This can be by exporting them from Testuff to your bug tracker, or by other communication methods your group is using to inform developers of defects. This can be even the Defects screen of Testuff, which developers can have access to.
The fixed defects are reported back, by changing their status in Testuff to Fixed or Resolved in the Defects screen. This can be automatically done from the integrated bug tracker, or manually in Testuff.
- To validate the fix, the QA lead or manager sends the fix for validation, by automatically creating a designated-validation test. This is easily done by clicking on the three dots menu on a defect and selecting the Assign to validate option. You may assign the validation to a user or a Lab.
- If the test passes, the defect can be set as Closed, otherwise it is Reopened, possibly with a comment on it, explaining the reason for that. Of course, you need to apply here your process and status values flow. Closing and/or re-opening is just one way to go about it.
As said, you might want to fine-tune this process, and adjust it to your own workflow and procedures. It does matter if you use a bug tracker or not, what’s the flow between QA and the Dev team, etc., but the above described is a relevant starting point.