ISTQB Throughout the Lifecycle 4 — Questions and Answers
Question 1: What is the primary benefit of involving testers in requirements reviews?
- Testers can write the requirements more accurately
- Defects in requirements are detected and corrected earlier (Correct answer)
- Testers can estimate development effort
- Requirements reviews replace functional testing
Correct answer: Defects in requirements are detected and corrected earlier
Early tester involvement in requirements reviews enables detection of ambiguous, incomplete, or contradictory requirements before they cascade into expensive downstream defects.
Question 2: Which SDLC characteristic makes automated test maintenance most challenging?
- Stable requirements throughout development
- Frequent changes to the application under test (Correct answer)
- Long release cycles with infrequent builds
- Dedicated test environments
Correct answer: Frequent changes to the application under test
Frequent application changes require constant test script updates, increasing maintenance overhead and making automated testing more costly to sustain.
Question 3: What distinguishes component integration testing from system integration testing?
- Component integration tests interfaces between units; system integration tests interfaces between subsystems or external systems (Correct answer)
- Component integration uses black-box techniques; system integration uses white-box
- Component integration is manual; system integration is automated
- Component integration is done by users; system integration by developers
Correct answer: Component integration tests interfaces between units; system integration tests interfaces between subsystems or external systems
Component integration testing focuses on interactions between individual components, while system integration testing verifies interactions between larger subsystems and external interfaces.
Question 4: A project switches from waterfall to agile mid-project. What is the most critical testing adaptation required?
- Eliminate all test documentation
- Move from end-of-cycle testing to continuous, sprint-based testing (Correct answer)
- Replace testers with developers
- Use only exploratory testing techniques
Correct answer: Move from end-of-cycle testing to continuous, sprint-based testing
Agile requires testing to occur continuously within each sprint rather than in a dedicated phase at the end, fundamentally changing the testing cadence and approach.
Question 5: What is the purpose of an exit criterion in a test level?
- Define when testing should begin
- Determine which tools to use for testing
- Specify conditions that must be met before testing can conclude (Correct answer)
- Identify who is responsible for testing
Correct answer: Specify conditions that must be met before testing can conclude
Exit criteria define the conditions that must be satisfied for a test level to be considered complete, ensuring adequate coverage before proceeding.
Question 6: In a risk-based testing approach applied throughout the lifecycle, what happens when a new high-risk area is identified late in development?
- Testing of that area is deferred to the next release
- Test priorities are adjusted to allocate more effort to the newly identified risk (Correct answer)
- The risk is ignored if testing has already begun
- All previous test results are discarded
Correct answer: Test priorities are adjusted to allocate more effort to the newly identified risk
Risk-based testing requires continuous reassessment; when new risks emerge, test priorities and resource allocation must be adjusted accordingly.
Question 7: Which statement best describes the relationship between test levels and development phases in a sequential model?
- Test levels are independent of development phases
- Each test level corresponds to a specific development activity (Correct answer)
- All test levels are executed simultaneously
- Test levels are only relevant in agile models
Correct answer: Each test level corresponds to a specific development activity
In sequential models like the V-model, each test level (unit, integration, system, acceptance) corresponds to a specific development phase (detailed design, high-level design, requirements, business needs).
What is the primary benefit of involving testers in requirements reviews?