ISTQB CTFL v4.0 Practice Test 3
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.
Question 21
During iteration planning and quality review, this issue appears: A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. Which testing action BEST addresses the stated issue? Select ONE best answer.
- Make test management and testing responsibilities explicit and collaborate with product owners, developers and testers for their respective decisions.
- Prepare test procedures, data, environment and execution schedule; then run, record deviations and perform test completion and archiving.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
Explanation
Correct Answer
D:This is the appropriate testing action: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery. The case involves A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
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. Here, A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
B: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 booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
C:That option would assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention, but it addresses a different concern. It follows the principle that Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software.
Question 22
A project team is deciding how to test this condition: A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. Which principle of software testing BEST explains the problem? Select ONE best answer.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software.
- An error is a human action, a defect is a flaw in a work product, and a failure is externally observable deviation caused when a defect is exercised.
- Testware consists of artifacts produced by testing and needs consistent ownership and configuration to support repeatable execution.
Explanation
Correct Answer
B:This is the relevant underlying rule: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software. In the situation described, A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
Incorrect Answers
A:That option would assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention, but it addresses a different concern. The practical response is to review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
C: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 booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
D: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 booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
Question 23
A foundation-level tester investigates: A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. Which specific test or review evidence MOST directly establishes what happened? Select ONE best answer.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Trace each acceptance rule and risk to identified test conditions and then to distinct cases, data and expected results.
- Follow one requirement into selected tests and results, then follow a failing test back to its requirement and linked defect.
- Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery.
Explanation
Correct Answer
D:This directly verifies the issue: Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery. The test should distinguish observed facts from the assumption that assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
Incorrect Answers
A:This shortcut is unsafe: Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention. It neglects the relevant behavior: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software.
B: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 booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
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 booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
Question 24
A test analyst considers this real project scenario: A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. 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.
- Stakeholders know who plans, executes, fixes and accepts testing evidence without shifting accountability informally.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Critical expectations are clarified before build and later testing confirms the implementation against those shared expectations.
Explanation
Correct Answer
D:This is the observable acceptance result: Critical expectations are clarified before build and later testing confirms the implementation against those shared expectations. It follows from the testing approach: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
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 booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
B: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 booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
C:This shortcut is unsafe: Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention. It neglects the relevant behavior: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software. For the scenario (A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.), the required evidence is: Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery.
Question 25
In a software test-design exercise, the following case arises: A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint. Which misleading assumption about early testing contributions and prevention MOST directly contributes to this problem and should be rejected? Select ONE best answer.
- Assume designed cases can be executed reliably with no setup, result recording or completion activities.
- Assume discovering an unexpected output means the tester has already identified the root cause and that a code patch needs no retest.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Assume a certified or documented quality process guarantees that every produced software component behaves correctly without product testing.
Explanation
Correct Answer
C:The correct principle is: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software.
Incorrect Answers
A:This is a misconception related to a different testing issue, namely Test implementation execution and completion, and is not the most direct assumption behind this case. Here, A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
B:This is a misconception related to a different testing issue, namely Testing and debugging as distinct activities, and is not the most direct assumption behind this case. Here, A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
D:This is a misconception related to a different testing issue, namely Quality assurance versus product testing, and is not the most direct assumption behind this case. Here, A booking service reaches system testing before anyone examines its cancellation rules and costly requirement gaps appear in the last sprint.
Question 26
A release manager requests independent testing evidence: A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. Which testing action BEST addresses the stated issue? Select ONE best answer.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Separate the human error, resulting work-product defect, observed execution failure and underlying cause before prioritizing preventive changes.
- 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.
Explanation
Correct Answer
C:This is the appropriate testing action: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery. The case involves A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
Incorrect Answers
A:This shortcut is unsafe: Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention. It neglects the relevant behavior: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software. For the scenario (A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.), the required evidence is: Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery.
B: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 mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
D: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 mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
Question 27
A software quality workshop reviews this situation: A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. Which principle of software testing BEST explains the problem? Select ONE best answer.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Independent perspectives reduce author bias but can introduce information gaps, delays or adversarial handoffs when collaboration breaks down.
- Quality assurance is process-oriented and preventive; testing is product-oriented quality control and supplies evidence about actual work products.
- Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software.
Explanation
Correct Answer
D:This is the relevant underlying rule: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software. In the situation described, A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
Incorrect Answers
A:This shortcut is unsafe: Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
B:This is an appropriate consideration for a different situation (Independent testing benefits and tradeoffs), but it does not directly resolve the one given here.
C: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 mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. The necessary control or test is: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
Question 28
A defect investigation documents this situation: A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. Which specific test or review evidence MOST directly establishes what happened? Select ONE best answer.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery.
- Inspect responsibility assignments, decisions about acceptance, defect ownership and records showing who verified each outcome.
- Trace each acceptance rule and risk to identified test conditions and then to distinct cases, data and expected results.
Explanation
Correct Answer
B:This check addresses the issue: Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery. The test should distinguish observed facts from the assumption that assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
Incorrect Answers
A:This shortcut is unsafe: Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention. For the scenario (A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.), the required evidence is: Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery.
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 mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
D: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 mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
Question 29
A tester and product owner review the following behavior: A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. 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.
- Both the development process and the product have appropriate independent evidence rather than one being used as a substitute for the other.
- The cases address every prioritized condition and the team can explain why each expected result demonstrates the rule.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
Explanation
Correct Answer
A:This is the observable acceptance result: Critical expectations are clarified before build and later testing confirms the implementation against those shared expectations. It follows from the testing approach: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery. The case is: A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
Incorrect Answers
B: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 mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
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.
D:It neglects the relevant behavior: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software. For the scenario (A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.), the required evidence is: Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery.
Question 30
During test preparation, a team encounters the following issue: A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story. Which TWO complementary steps together provide the most appropriate response and a direct test of its effectiveness? Select TWO answers.
- Make test management and testing responsibilities explicit and collaborate with product owners, developers and testers for their respective decisions.
- Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery.
- Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention.
- Trace each acceptance rule and risk to identified test conditions and then to distinct cases, data and expected results.
- Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery.
Explanation
Correct Answers
B:This check addresses the issue: Examine dates of stakeholder reviews, rejected ambiguous requirements, defects prevented and rework or release delays traced to late discovery. The test should distinguish observed facts from the assumption that assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention. The intended testing outcome is: Critical expectations are clarified before build and later testing confirms the implementation against those shared expectations.
E:This is the appropriate testing Recommended action: Review requirements and examples early, agree testable expectations with stakeholders and run suitable testing throughout development instead of waiting until delivery. The case involves A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
Incorrect Answers
A:This is a misconception related to a different testing issue, namely Test roles and collaborative ownership, and is not the most direct assumption behind this case. Here, A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
C:This shortcut is unsafe: Assume testing adds value only after executable code exists, so discussions of requirements cannot contribute to defect prevention. It neglects the relevant behavior: Earlier quality feedback can prevent or detect defects when changes are cheaper, and the value of testing is not limited to executing software. In this scenario: aration, a team encounters the following issue: A mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.
D: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 mobile product ships after late tests reveal a missing accessibility behavior already visible in the original user story.