Question 1. An agile team with experienced testers works on a product whose requirements change every sprint. Test cases must stay maintainable and leave room for the tester's judgement during execution. Which kind of test case suits this situation best?
- Option A: Low-level test cases with concrete input values and exact expected results
- Option B: High-level test cases without concrete values for inputs and expected results
- Option C: Test charters only, with no test cases at all
- Option D: Low-level test cases generated from the code
Show answer and explanation
Correct answer: B. High-level test cases without concrete values for inputs and expected results
High-level test cases describe what to test without fixing concrete data, so they need less rework when requirements change and use the tester's experience. Low-level test cases are preferred when reproducibility, auditability or automation matter more.
- A (incorrect)Low-level test cases suit inexperienced testers, regulatory needs or automation, but they are costly to maintain when requirements change often.
- B (correct)Correct. High-level (logical) test cases are easier to maintain under changing requirements and let experienced testers vary the data during execution.
- C (incorrect)Charters support session-based testing, but the question asks which kind of test case fits; dropping test cases entirely is not implied by the scenario.
- D (incorrect)Deriving test cases from code is a white-box approach and does not address maintainability under changing requirements.
Reference: ISTQB: CTAL-TA Syllabus v4.0 (opens in a new tab)

