ISTQB ISTQB-AL-TA Free Practice Questions — Page 1

Correct Answer: A. At the beginning of the project.

In Agile projects, the Test Analyst's involvement starts at the beginning of the project, not at a later phase. Agile promotes the "whole team" approach, meaning testers participate from day one — joining sprint planning, backlog refinement, and story analysis. Early involvement allows testers to review and influence user stories, identify testability issues, and define acceptance criteria before development begins. Waiting until the first iteration (B) would miss critical input during initial planning and story elaboration. Waiting for sign-off (C) is a waterfall mindset and contradicts Agile's collaborative nature. Starting in parallel with coding (D) is too late and reduces the tester's ability to shift-left and prevent defects.

Correct Answer: C. Applying test techniques to reduce the likelihood of omitting important test conditions.

During Test Analysis, the primary goal is to identify what to test — this is done by analyzing the test basis and deriving test conditions. Applying test techniques (e.g., equivalence partitioning, boundary value analysis) during this stage helps ensure no important test conditions are missed. Option A describes Test Design activities (producing test cases and test data), not Test Analysis. Option B relates to Test Planning, where schedules and milestones are defined. Option D is incorrect because one test condition should cover one specific condition — mapping multiple risks into one condition to reduce maintenance is poor practice and risks leaving gaps in coverage.

Correct Answer: A. a and b.

Stakeholder reviews of test conditions and test cases serve two key purposes: verifying that testers correctly understood the requirements (a), and confirming that the test basis is adequately covered (b). If testers misunderstood requirements, test conditions will be wrong regardless of technique quality — stakeholder review catches this early. Adequate coverage verification (b) ensures no important areas are untested. Option c (project schedule) is a project management concern, not a reason for reviewing test conditions. Option d (assessing test analyst skill) is not a purpose of test case review. Option e (enabling the test manager to select test approaches) is a planning activity done before test design, not after.

Correct Answer: B. Project A - High level test cases. Project B - Low level test cases.

Project A suits high-level test cases because: the changes are minor UI updates, the testers already know the system well (they were involved in development), and tests are manually executed by experienced staff — formal detail is unnecessary overhead. Project B requires low-level test cases for three reasons: (1) test automation requires precise, unambiguous steps; (2) the algorithm is complex and regression risk is high; (3) an external auditor will review the project, requiring formal, traceable documentation. Low-level test cases provide the detail needed for automation scripts and audit evidence. High-level cases would be insufficient for automated test implementation and external scrutiny.

Correct Answer: B. Project C - High level test cases. Project D - Low level test cases.

For Project C, the most effective approach is high-level test cases (also known as logical test cases). Since the project has a history of vague and inconsistent requirements, writing detailed "low-level" steps prematurely would lead to constant rework as requirements are clarified. High-level cases allow test analysts to document the general testing objectives and "what" to test while the more formal requirements reviews are still maturing, providing flexibility without getting bogged down in specifics that are likely to change. For Project D, the recommendation is low-level test cases. This project requires a strong regression pack that will initially be run manually but eventually automated. Low-level test cases provide the necessary detail—including specific input data and expected results—to ensure consistency during manual regression cycles. This high level of detail is a prerequisite for automation, as a script requires exact steps and data to execute correctly. Following ISTQB best practices, low-level cases reduce the risk of different testers executing the same test differently, which is vital for reliable regression testing.