Verification and Validation
Verification and validation are two complementary questions every product must answer before release.
On this page · 5 min · Beginner
On this page
- Learning objectives
- Explanation
- Code example
- Step by step
- Real-world use
- Common mistakes
- Best practices
- Remember this
- Practice exercise
- Mini quiz
- Related topics
- My notes
- Reading time
- 5 min
- Difficulty
- Beginner
- Updated
- Oct 29, 2026
Related tutorials
Learning objectives#
- Define verification and validation
- Distinguish static and dynamic testing
- Describe reviews, walkthroughs and inspections
- Choose the right activity for each stage
Explanation#
Verification: “Are we building the product right?” Checks work products against specifications without running code — reviews of requirements, designs and code (static testing).
Validation: “Are we building the right product?” Runs the software to check it meets user needs (dynamic testing), up to user acceptance testing.
Static techniques: informal reviews, walkthroughs (author leads), technical reviews and inspections (formal, with roles and checklists).
Code example: One feature, both questions#
Feature: "Users can reset their password by email."
Verification (static)
• Review requirement: Is the link expiry time specified? → missing, raise question
• Review design: Is the reset token single-use? → yes
• Code review: Is the token random and long enough? → yes
Validation (dynamic)
• Request reset → email arrives → link works → new password accepted
• Use the link twice → second attempt rejected
• Ask real users: can they find "Forgot password?" → 2 of 5 could not → move the link
Verification caught a gap in the requirement; validation found a usability problem no specification described.
This example is illustrative. Copy or download it and run it in your own environment; the expected output is shown above.
Step-by-step explanation#
- Static reviews find gaps before code exists.
- Design and code reviews check against the spec.
- Dynamic tests run the real feature.
- User feedback validates that it solves the real need.
Real-world use case#
Requirement reviews with the business analyst prevent misunderstandings that would otherwise become expensive bugs.
Common mistakes#
Many defects are cheaper to catch in a 30-minute requirement review.
Verification = right product built right (specs); validation = right product (user needs).
Best practices#
- Review requirements with a checklist
- Join design and code reviews
- Include real users in validation
- Record review findings like defects
Remember this#
Verification: building it right (static).
Validation: building the right thing (dynamic).
Reviews are the cheapest testing.
Practice exercise#
Your task: Is a code review verification or validation?
Show solution
Verification — it checks the code against specifications without executing it.
Mini quiz#
Which activity is validation?
Want more? Practise all Manual Testing MCQs · Manual Testing interview questions
My notes#
Saved in this browser.