Actual Result
The actual result is the observed outcome produced when a test case is executed.
“The behavior produced/observed when a component or system is tested.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Actual Result?
During test execution, testers compare the actual result with the expected result. Any difference may indicate a defect or an issue that requires investigation.
Recording results: Actual results should clearly describe what happened during execution.
Comparison: Actual and expected results together determine whether a test passes or fails.
Defect reporting: Accurate actual results improve the quality of defect reports.
Real World Example
A hospital medication system shows a different dosage warning in test than the one specified by the clinical safety rule.
The team needs precise language to separate what was observed, what should have happened, and whether the difference represents a reportable issue. Actual result provides that distinction.
The tester records the steps, data, observed behavior, expected behavior, and evidence so triage can focus on patient safety impact instead of vague descriptions.
The issue is handled faster because Actual result helps everyone discuss the problem using a shared testing vocabulary.
Practice Questions
Question 1
A tester executes a test case for a login feature. The expected result is 'User is redirected to the dashboard.' The system displays 'Invalid credentials' instead. What is the actual result?
Question 2
Why is it important to document the actual result with specific details rather than just 'pass' or 'fail'?
Test your knowledge with real ISTQB-style questions
You’ve learned Actual Result. Test your understanding with topic-specific questions in our Mock Exams.