Failed
Failed describes the status of a test case, test, or activity that did not achieve its expected result or acceptance criteria.
“The status of a test result if the actual result does not match the expected result.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Failed?
A failed test indicates that the observed outcome differs from the expected outcome. Further investigation is needed to determine whether the cause is a software defect, environment issue, or test problem.
Result comparison: A failure is identified by comparing actual and expected results.
Investigation: The cause of a failed test must be analyzed before reporting a defect.
Status reporting: Failed tests are tracked to support quality assessment and defect management.
Real World Example
A regulated product team is preparing a release where Failed appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Failed 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 Failed and similar ideas.
The page becomes useful in practice because Failed is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Failed in the context of ISTQB terminology?
Question 2
A tester needs to explain Failed to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Failed. Test your understanding with topic-specific questions in our Mock Exams.