Testrix

Defects retesting is done to make sure that the tests cases which failed in last execution are passing after the defects against those failures are fixed.

Defect is ready for re-test by QA when all criteria are met:
Defect record has [Status] = "Ready for testing" in the bug tracking system.
Defect fix is delivered to the system environment where it is supposed to be retested. [Target version] (or fixed version) is populated accordingly in the bug tracking system.
Defect has a Resolution (set up by dev)
Defect has a comment with impact analysis or/and way for implementation by dev - the option may depend on a defect or project process

Defect re-testing process:
When fix was applied by the resolver

1. QA engineer changes the defect status from "Ready for testing" to "Testing"
2. Execute steps from the Defect report to check that it was fixed. Repeat the test with multiple data sets.
3. Execute regression tests for the related test cases or test scenarios to make sure that no critical issues appeared in the related functionality. Include:
   3.1 Tests related to the same functional area or module
   3.2 Tests related to connected areas or modules (e.g. authorization and registration, reading and updating data etc.)
   3.3 Test generated based on the impact analysis from the developer, who investigated and fixed the defect.