ISTQB CTFL v4.0 Practice Test 2
Question 10
During test preparation, a team encounters the following issue: A payroll product has a detailed bug list yet the sponsor cannot tell which acceptance conditions remain unverified before launch. Which TWO complementary steps together provide the most appropriate response and a direct test of its effectiveness? Select TWO answers.
- Compare the stated test objectives with acceptance criteria, risk exposures, open findings and evidence from completed test activities.
- Review and vary tests as the product evolves, and assess business fitness as well as observed defects before declaring success.
- Assume a large executed test count by itself proves the product is defect-free and suitable for its intended use.
- Inspect the input-space estimate, selected partitions, affected risks, boundary coverage and the rationalized untested combinations.
- Define explicit testing objectives including risk information, defect discovery and confidence in specified requirements, and report evidence against those objectives.
Explanation
Correct Answers
A:This check addresses the issue: Compare the stated test objectives with acceptance criteria, risk exposures, open findings and evidence from completed test activities. The test should distinguish observed facts from the assumption that assume a large executed test count by itself proves the product is defect-free and suitable for its intended use. The intended testing outcome is: Decision makers receive an evidence-based account of what was tested, what remains uncertain and which release risks are accepted.
E:This is the appropriate testing Recommended action: Define explicit testing objectives including risk information, defect discovery and confidence in specified requirements, and report evidence against those objectives. The case involves A payroll product has a detailed bug list yet the sponsor cannot tell which acceptance conditions remain unverified before launch.
Incorrect Answers
B:This is a misconception related to a different testing issue, namely Pesticide paradox and absence of errors fallacy, and is not the most direct assumption behind this case. Here, A payroll product has a detailed bug list yet the sponsor cannot tell which acceptance conditions remain unverified before launch.
C:This shortcut is unsafe: Assume a large executed test count by itself proves the product is defect-free and suitable for its intended use. It neglects the relevant behavior: Testing evaluates quality and supplies information for decisions; running many test cases alone is not a sufficient test objective or quality guarantee. In this scenario: During test preparation, a team encounters the following issue: A payroll product has a detailed bug list yet the sponsor cannot tell.
D:This is a misconception related to a different testing issue, namely Exhaustive testing impossibility and selection, and is not the most direct assumption behind this case. Here, A payroll product has a detailed bug list yet the sponsor cannot tell which acceptance conditions remain unverified before launch.
Question 11
During iteration planning and quality review, this issue appears: A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. Which testing action BEST addresses the stated issue? Select ONE best answer.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
- Analyze the test basis to identify testable conditions, then design coverage items and concrete cases from those conditions before execution.
- Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
Explanation
Correct Answer
D:This is the appropriate testing action: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix. The case involves A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.
Incorrect Answers
A:That option would assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest, but it addresses a different concern. It follows the principle that Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect.
B:This is an appropriate consideration for a different situation (Early testing contributions and prevention), but it does not directly resolve the one given here. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
C:This is an appropriate consideration for a different situation (Distinguishing test analysis and test design), but it does not directly resolve the one given here.
Question 12
A project team is deciding how to test this condition: A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. Which principle of software testing BEST explains the problem? Select ONE best answer.
- Testing is performed through roles and tasks; clear responsibility and communication prevent ambiguity about evidence, approval and correction.
- Testware consists of artifacts produced by testing and needs consistent ownership and configuration to support repeatable execution.
- Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
Explanation
Correct Answer
C:This is the relevant underlying rule: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect. In the situation described, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Test roles and collaborative ownership), but it does not directly resolve the one given here.
B:This is an appropriate consideration for a different situation (Testware inventory and configuration), but it does not directly resolve the one given here. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
D:That option would assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest, but it addresses a different concern. The practical response is to record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
Question 13
A foundation-level tester investigates: A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. Which specific test or review evidence MOST directly establishes what happened? Select ONE best answer.
- Inspect environment readiness, ordered procedures, executed-result logs, defect links and the archived completion report.
- Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- Compare the stated test objectives with acceptance criteria, risk exposures, open findings and evidence from completed test activities.
Explanation
Correct Answer
B:This directly verifies the issue: Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario. The test should distinguish observed facts from the assumption that assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Test implementation execution and completion), but it does not directly resolve the one given here. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.
C:This shortcut is unsafe: Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest. It neglects the relevant behavior: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect.
D:This is an appropriate consideration for a different situation (Testing objectives tied to decision-making), but it does not directly resolve the one given here.
Question 14
A test analyst considers this real project scenario: A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. Which observed result BEST demonstrates that the testing activity met its stated objective? Select ONE best answer.
- The cases address every prioritized condition and the team can explain why each expected result demonstrates the rule.
- The chosen set targets important behavior and residual untested risks are visible to decision makers within the allocated time.
- The cause is corrected and the previously failing test passes with traceable evidence, with regression scope considered separately.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
Explanation
Correct Answer
C:This is the observable acceptance result: The cause is corrected and the previously failing test passes with traceable evidence, with regression scope considered separately. It follows from the testing approach: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Distinguishing test analysis and test design), but it does not directly resolve the one given here. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.
B:This is an appropriate consideration for a different situation (Exhaustive testing impossibility and selection), but it does not directly resolve the one given here. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
D:This shortcut is unsafe: Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest. It neglects the relevant behavior: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect. For the scenario (A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.), the required evidence is: Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario.
Question 15
In a software test-design exercise, the following case arises: A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it. Which misleading assumption about testing and debugging as distinct activities MOST directly contributes to this problem and should be rejected? Select ONE best answer.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- Assume writing a click sequence immediately from a story title is equivalent to identifying every necessary test condition.
- Assume a test script alone is all the testware required and that uncontrolled edits cannot change testing conclusions.
- Assume maximum organizational separation always guarantees more effective testing regardless of communication or domain understanding.
Explanation
Correct Answer
A:The correct principle is: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect.
Incorrect Answers
B:This is a misconception related to a different testing issue, namely Distinguishing test analysis and test design, and is not the most direct assumption behind this case. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.
C:This is a misconception related to a different testing issue, namely Testware inventory and configuration, and is not the most direct assumption behind this case. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.
D:This is a misconception related to a different testing issue, namely Independent testing benefits and tradeoffs, and is not the most direct assumption behind this case. Here, A tester observes that invoice totals double after a retry, but a developer says the tester must patch the underlying tax calculation before reporting it.
Question 16
A release manager requests independent testing evidence: A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. Which testing action BEST addresses the stated issue? Select ONE best answer.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- Define explicit testing objectives including risk information, defect discovery and confidence in specified requirements, and report evidence against those objectives.
- Maintain bidirectional links among requirements, risk conditions, test cases, execution outcomes and defects, using them for change impact.
- Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
Explanation
Correct Answer
D:This is the appropriate testing action: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix. The case involves A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
Incorrect Answers
A:This shortcut is unsafe: Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest. It neglects the relevant behavior: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect. For the scenario (A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.), the required evidence is: Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario.
B:This is an appropriate consideration for a different situation (Testing objectives tied to decision-making), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
C:This is an appropriate consideration for a different situation (Bidirectional traceability of tests and requirements), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
Question 17
A software quality workshop reviews this situation: A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. Which principle of software testing BEST explains the problem? Select ONE best answer.
- Quality assurance is process-oriented and preventive; testing is product-oriented quality control and supplies evidence about actual work products.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- Testing is performed through roles and tasks; clear responsibility and communication prevent ambiguity about evidence, approval and correction.
- Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect.
Explanation
Correct Answer
D:This is the relevant underlying rule: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect. In the situation described, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Quality assurance versus product testing), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
B:This shortcut is unsafe: Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
C:This is an appropriate consideration for a different situation (Test roles and collaborative ownership), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
Question 18
A defect investigation documents this situation: A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. Which specific test or review evidence MOST directly establishes what happened? Select ONE best answer.
- Follow one requirement into selected tests and results, then follow a failing test back to its requirement and linked defect.
- Compare the stated test objectives with acceptance criteria, risk exposures, open findings and evidence from completed test activities.
- Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
Explanation
Correct Answer
C:This check addresses the issue: Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario. The test should distinguish observed facts from the assumption that assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Bidirectional traceability of tests and requirements), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
B:This is an appropriate consideration for a different situation (Testing objectives tied to decision-making), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
D:This shortcut is unsafe: Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest. For the scenario (A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.), the required evidence is: Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario.
Question 19
A tester and product owner review the following behavior: A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. Which observed result BEST demonstrates that the testing activity met its stated objective? Select ONE best answer.
- Critical expectations are clarified before build and later testing confirms the implementation against those shared expectations.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- The cause is corrected and the previously failing test passes with traceable evidence, with regression scope considered separately.
- The report identifies the failure condition and underlying defect without confusing symptoms, the responsible person or the opportunity for prevention.
Explanation
Correct Answer
C:This is the observable acceptance result: The cause is corrected and the previously failing test passes with traceable evidence, with regression scope considered separately. It follows from the testing approach: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix. The case is: A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Early testing contributions and prevention), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
B:It neglects the relevant behavior: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect. For the scenario (A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.), the required evidence is: Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario.
D:This is an appropriate consideration for a different situation (Error defect failure and root cause chain), but it does not directly resolve the one given here. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. The necessary control or test is: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
Question 20
During test preparation, a team encounters the following issue: A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test. Which TWO complementary steps together provide the most appropriate response and a direct test of its effectiveness? Select TWO answers.
- Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix.
- Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- Compare recent change areas and incidents to test coverage, new test ideas and the mapped essential business outcomes.
- Version and identify test cases, data, harnesses, expected results and environment baselines as controlled testware.
Explanation
Correct Answers
A:This is the appropriate testing Recommended action: Record reproducible failure evidence in testing, then let debugging locate and correct the cause, followed by confirmation testing of the fix. The case involves A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
B:This check addresses the issue: Preserve the failed input and actual output, the developer diagnosis, patch reference and rerun of the exact original failure scenario. The test should distinguish observed facts from the assumption that assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest. The intended testing outcome is: The cause is corrected and the previously failing test passes with traceable evidence, with regression scope considered separately.
Incorrect Answers
C:This shortcut is unsafe: Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest. It neglects the relevant behavior: Testing can reveal failures and their conditions; debugging diagnoses the cause and changes code, while confirmation testing checks that the change solved the defect. In this scenario: ation, a team encounters the following issue: A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
D:This is a misconception related to a different testing issue, namely Pesticide paradox and absence of errors fallacy, and is not the most direct assumption behind this case. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.
E:This is a misconception related to a different testing issue, namely Testware inventory and configuration, and is not the most direct assumption behind this case. Here, A developer fixes a date parsing error and announces that the defect is resolved without rerunning the original failing test.