Question 580
At fictional Elmstone Software, the quality team is reviewing a change to its project collaboration platform. After fixing a tax calculation bug, the team reruns every unrelated screen but never checks the exact failed tax case. Which recurring practice would most directly reduce the chance of this situation recurring?
Explanation
Correct Answer
The recurring safeguard is to rerun the original failing case as confirmation, then execute relevant surrounding regression coverage. The specific expected result is: the specific former failure passes and related unaffected calculations remain correct.
Incorrect Answers
Maintaining role-and-resource negative tests after authorization changes supports security testing. In the source scenario, after fixing a tax calculation bug, the team reruns every unrelated screen but never checks the exact failed tax case; the preventive practice is to link each fixed defect to its confirmation case and impacted regression subset.
Maintaining acceptance criteria owned by relevant business representatives supports acceptance testing. In the source scenario, after fixing a tax calculation bug, the team reruns every unrelated screen but never checks the exact failed tax case; the preventive practice is to link each fixed defect to its confirmation case and impacted regression subset.
Adding relevant regression checks to each story's definition of done supports iterative development testing. In the source scenario, after fixing a tax calculation bug, the team reruns every unrelated screen but never checks the exact failed tax case; the preventive practice is to link each fixed defect to its confirmation case and impacted regression subset.