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

Questions 16–20

1. 16expert · hard

   A test manager is comparing two test suites to decide which one is more effective for a critical module. Suite A detects 90% of seeded faults, while Suite B detects 70% of seeded faults. However, Suite A has a much higher false positive rate and requires significantly more time to execute. Which conclusion is most justified?

   • ASuite A is likely more effective at finding defects, but the higher false positive rate and execution time may reduce its overall value.
   • BThe suite with the higher detection rate is always the best choice regardless of other factors.
   • CThe seeded fault detection rates are not comparable because the suites were not run on the same code.
   • DSuite B is more effective because it has a lower false positive rate and is faster.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A test manager wants to evaluate whether the current regression test suite is thorough enough to support a release decision. The team has time to run the suite only once more. Which approach best uses fault seeding to inform this decision?

   • ASeed faults that are easy to find to ensure a high detection rate, which will demonstrate the suite is thorough.
   • BSeed only the most complex faults that are likely to be missed, and if any are found, consider the suite adequate.
   • CSeed a representative set of known faults, run the suite, and compare the detection rate of seeded faults to the historical detection rate of real faults.
   • DRun the suite once to establish a baseline, then seed faults and run again to see if the detection rate improves.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A test team is implementing fault seeding for the first time. They have selected a set of realistic faults to insert. What is the correct sequence of steps for the fault seeding process?

   • AEstimate remaining defects first, then insert seeded faults to confirm the estimate.
   • BInsert seeded faults, run the test suite, identify which seeded faults were detected, then use the detection ratio to estimate remaining defects.
   • CInsert seeded faults, then manually review the code to find them, and use the review results to estimate remaining defects.
   • DRun the test suite first to establish a baseline, then insert seeded faults and run again to see if the detection rate improves.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   In fault seeding, what does the detection rate of seeded faults help testers evaluate?

   • AThe skill level of the individual testers
   • BThe ability of the test suite to uncover defects
   • CThe number of test cases that need to be automated
   • DThe efficiency of the test environment in terms of execution speed
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A project manager asks the test lead to justify the effort of fault seeding. The test lead explains that fault seeding can help predict the number of defects that will be reported by users after release. Which statement best supports this claim?

   • AFault seeding provides a direct count of the defects that will be found by users.
   • BFault seeding guarantees that all defects will be found before release, so no user-reported defects are expected.
   • CFault seeding increases the number of defects found during testing, which reduces the number of defects in production.
   • DBy comparing the detection rate of seeded faults to real defects found during testing, the team can estimate the number of undetected real defects that may surface in production.
   Reveal Solution Discussion Select an answer first