Test Execution
Test execution is the activity of running test cases, comparing actual results with expected results, and recording outcomes.
“The activity that runs a test on a component or system producing actual results.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Test Execution?
During execution, testers identify defects, collect evidence, and verify whether the software behaves as specified.
Execution phase: Planned test cases are performed.
Result comparison: Actual and expected outcomes are evaluated.
Defect reporting: Failures are documented for investigation.
Real World Example
A regulated product team is preparing a release where Test execution appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Test execution 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 Test execution and similar ideas.
The page becomes useful in practice because Test execution is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Test execution in the context of ISTQB terminology?
Question 2
A tester needs to explain Test execution to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Test Execution. Test your understanding with topic-specific questions in our Mock Exams.