Test results are reported as "Requirements tested, passed, and failed". What test strategy are you using? [1]

An analytical test strategy involves analyzing a specific test basis, such as requirements or risks, to identify test conditions and design test cases. When utilizing a requirements-based analytical strategy, the testing effort is directly traced back to the original requirements. Consequently, test progress and results are reported against this basis, utilizing metrics such as "requirements tested, requirements passed, and requirements failed" to demonstrate coverage and overall quality to stakeholders.

A. Model-based: This strategy relies on building formal mathematical or state models, and results are reported based on model coverage rather than direct textual requirements.
B. Exploratory: This is a reactive strategy focusing on concurrent learning and test design, not typically driven by formal upfront requirements reporting.
D. Reactive: In a reactive strategy, tests are designed dynamically after receiving the software, reacting to the actual system rather than pre-analyzed requirements.

1. ISTQB Certified Tester Advanced Level - Test Manager Syllabus (v2012), Section 2.3.2 "Test Strategies", pp. 24-25.

2. ISTQB Certified Tester Foundation Level Syllabus (v4.0), Section 5.2.1 "Test Strategies and Approaches".