Expected Result
An expected result is the predicted outcome that should occur when a test case is executed under specified conditions.
“The observable predicted behavior of a test item under specified conditions based on its test basis.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Expected Result?
Expected results define the correct system behavior and provide the basis for determining whether a test passes or fails.
Reference outcome: Derived from requirements, specifications, or business rules.
Comparison: Actual results are evaluated against expected results.
Defect detection: Differences may indicate software defects.
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. Expected 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 Expected result helps everyone discuss the problem using a shared testing vocabulary.
Practice Questions
Question 1
Which statement BEST describes Expected result in the context of ISTQB terminology?
Question 2
A tester needs to explain Expected result to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Expected Result. Test your understanding with topic-specific questions in our Mock Exams.