Requirements-based Testing
Requirements-based testing is a test design approach in which test cases are derived directly from documented requirements.
“A test approach in which test conditions are based on requirements.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Requirements-based Testing?
The objective is to verify that every requirement has been implemented correctly and is covered by one or more test cases.
Traceability: Tests map directly to requirements.
Coverage: Ensures requirements are verified systematically.
Verification: Confirms implemented behavior matches specifications.
Real World Example
A regulated product team is preparing a release where Requirements-based testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Requirements-based testing as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Requirements-based testing and similar ideas.
The page becomes useful in practice because Requirements-based testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Requirements-based testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Requirements-based testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Requirements-based Testing. Test your understanding with topic-specific questions in our Mock Exams.