A defect in a SUT has been resolved and validated by an automated defect re-test in the current release of the software. This retest has now been added to the automated regression test suite. Which…

Question

Options

• AAutomated defect confirmation testing is not effective at confirming that the resolved defect will
• BThe configuration management process does not properly control the synchronization between
• CThe automated regression test suite is not run consistently for future releases.
• DThe automated regression test suite has a narrower scope of functionality

• A
  5% (2)
• B
  3% (1)
• C
  84% (31)
• D
  8% (3)

Explanation

Option C is correct because adding a test to a regression suite only provides protection if that suite is actually executed on future releases. If the suite is skipped, run selectively, or applied inconsistently, the defect can silently reappear without detection - the test exists but isn't there to catch anything.

Why the distractors fail:

• A is wrong because the question explicitly states the defect was validated by the automated re-test - so the confirmation testing worked fine; its effectiveness isn't the issue.
• B is wrong because configuration management synchronization issues are a separate concern; the scenario already confirms the fix was properly validated and the test added to the suite.
• D is wrong because scope of coverage is irrelevant here - the suite already contains a specific test for this exact defect, so a narrower scope wouldn't cause that particular test to miss the regression.

Memory tip: Think of a regression suite like a security camera - installing it doesn't protect you if no one ever reviews the footage. The test must be run consistently, not just exist.

No community discussion yet for this question.