Reactive Testing
Reactive testing is testing that is designed and executed in response to actual events, observations, or defects discovered during test execution.
“A test approach that dynamically responds to the behavior of a test object and to test results being obtained.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Reactive Testing?
Testers continuously learn from system behavior and modify their testing approach to investigate newly identified risks or failures.
Observation driven: Testing evolves during execution.
Flexible execution: New tests are created as knowledge increases.
Defect investigation: Additional testing follows unexpected results.
Real World Example
A regulated product team is preparing a release where Reactive testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Reactive 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 Reactive testing and similar ideas.
The page becomes useful in practice because Reactive testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Reactive testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Reactive testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Reactive Testing. Test your understanding with topic-specific questions in our Mock Exams.