Multiple choice technology testing

Consider the following statements about early test design: i. early test design can prevent fault multiplication ii. faults found during early test design are more expensive to fix iii. early test design can find faults iv. early test design can cause changes to the requirements v. early test design takes more effort

  1. i, iii & iv are true, ii & v are false

  2. iii is true, i, ii, iv & v are false

  3. iii & iv are true, i, ii & v are false

  4. i, iii, iv & v are true, ii is false
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Early test design prevents fault multiplication (catching requirements issues before implementation), finds faults early when cheaper to fix, and can cause requirement changes based on test insights. Statement ii is false - early faults are LESS expensive to fix. Statement v is situational - early design can reduce total effort despite upfront investment.

AI explanation

Early test design (creating test cases/conditions early in the lifecycle, even before code is written) is valuable because it can find faults directly in requirements/design documents (iii), and by catching ambiguities or errors that early it prevents those faults from multiplying downstream into code and later test phases (i) — but doing so thoroughly can also surface gaps or contradictions that force changes to the requirements themselves (iv). Statement (ii) is false because the whole premise of 'early' testing is that faults found early are cheaper, not more expensive, to fix (cost of fixing defects rises the later they're found). Statement (v) is false in the sense intended here — while early test design takes effort, it's not counted as a downside in this standard test-theory framing, which emphasizes its net cost-saving benefit.

Keep practicing — related questions