Which of the following success factors for a test automation project is TRUE?

Question

Options

• AAutomated tests must be designed to capture only the data that is strictly needed for comparing
• BThe test cases to be automated first must always be selected based on the number of times a
• CThe test cases to be automated must have a high dependency on particular data values
• DAutomated tests that fail due to changes in the requirements of the SUT should be promptly fixed

• A
  2% (1)
• B
  4% (2)
• C
  8% (4)
• D
  87% (45)

Explanation

Option D is correct because maintaining automated tests when requirements change is essential to keeping the test suite trustworthy and valuable - a failing test caused by a legitimate requirement change is not a defect in the SUT, and leaving it broken erodes confidence in the entire suite.

Why the distractors are wrong:

• A is false: automated tests often need to capture more than the minimum data, including context for debugging failures, traceability, and audit trails.
• B is incomplete/false as stated: frequency of execution is one criterion for prioritizing automation, but not the only or always dominant one - risk, complexity, and stability also matter.
• C is the opposite of good practice: high data dependency makes tests fragile and hard to maintain; well-designed automated tests should be data-independent or use parameterized/data-driven approaches.

Memory tip: Think of automated tests as living documentation - when the requirements evolve, the tests must evolve with them (D), and they should be built to be stable (low data dependency, not high - eliminating C) and informative (capturing enough context, not just the bare minimum - eliminating A).

No community discussion yet for this question.