Validation
Validation is the process of confirming that a software product fulfills its intended use and satisfies user and business needs.
“Confirmation by examination that a work product matches a stakeholder's needs.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Validation?
Validation answers the question, "Are we building the right product?" by ensuring the delivered solution meets stakeholder expectations.
User focused: Verifies intended business value.
Business validation: Confirms user needs are satisfied.
Acceptance support: Common during acceptance testing.
Real World Example
A regulated product team is preparing a release where Validation appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Validation 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 Validation and similar ideas.
The page becomes useful in practice because Validation is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Validation in the context of ISTQB terminology?
Question 2
A tester needs to explain Validation to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Validation. Test your understanding with topic-specific questions in our Mock Exams.