Why is it important to seed faults that are representative of real defects?

To ensure the estimation of remaining defects is accurate

To make the test suite appear more effective than it is

To avoid introducing too many faults into the code

To reduce the time needed to run the test suite

What is the primary purpose of fault seeding in software testing?

To replace real defects with artificial ones to simplify debugging

To measure the performance of the system under artificial fault conditions

To permanently remove all defects from the code before release

To estimate the number of remaining defects and evaluate test effectiveness

A test team used fault seeding to estimate remaining defects in a system. They seeded 50 faults, and the test suite found 40 of them. They also found 10 real defects. The team is about to release the system. Which additional information would most improve the reliability of the estimate?

The time it took to execute the test suite and the number of test cases that failed.

The distribution of the seeded faults across the codebase compared to the distribution of real defects found in previous releases.

The total number of test cases in the suite and the code coverage achieved.

The names of the testers who executed the suite and their experience levels.

A test team is planning to seed faults into a legacy system to estimate remaining defects. The system has a history of defects in boundary conditions and error handling. Which set of seeded faults would provide the most meaningful estimation?

Faults that are intentionally obscure and difficult to find, to challenge the test team.

Only faults that are easy to detect, to ensure a high detection rate and a low estimated remaining defect count.

A mix of faults similar to those found in production, including boundary and error-handling defects, plus a few simple logic errors.

Only boundary condition faults, since they are the most common in this system.

How can tools assist in fault seeding?

By removing all real defects from the code before testing

By automatically inserting faults into the code and tracking their detection

By generating test cases that are guaranteed to find all faults

By replacing the need for manual test execution

Certified Tester Advanced Level Technical Test Analyst

Domain 6Objective 3

Fault Seeding Tools CTAL-TTA Practice Questions (Page 3)

Part of the Domain 6: Test Tools and Automation domain, which makes up ~25% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~13–20 in this domain), expect 1–2 from this objective — we provide 27 practice questions to prepare you well beyond it. (estimate)

27questions here

6free pages

7concepts

Questions 11–15

11foundation · easy
Why is it important to seed faults that are representative of real defects?
Select an answer first
12foundation · easy
What is the primary purpose of fault seeding in software testing?
Select an answer first
13expert · hard
A test team used fault seeding to estimate remaining defects in a system. They seeded 50 faults, and the test suite found 40 of them. They also found 10 real defects. The team is about to release the system. Which additional information would most improve the reliability of the estimate?
Select an answer first
14application · medium
A test team is planning to seed faults into a legacy system to estimate remaining defects. The system has a history of defects in boundary conditions and error handling. Which set of seeded faults would provide the most meaningful estimation?
Select an answer first
15foundation · easy
How can tools assist in fault seeding?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-TTA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CTAL-TTA” is a trademark of its owner, used for identification only.