What is the difference between verification and validation in testing?
- verification
- validation
- testing fundamentals
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Verification: "Are we building the product right?" Checks that the implementation matches the specification. Examples: code reviews, unit tests, integration tests, static analysis. Validation: "Are we building the right product?" Checks that the product meets user needs. Examples: user acceptance testing (UAT), beta testing, usability testing, A/B testing. Both are necessary. You can build a perfectly coded feature (verification passes) that nobody wants to use (validation fails). QA covers both: technical correctness and user value.
What interviewers listen for
- Risk-based prioritisationYou can defend skipping coverage on a path because the risk maths supports it.
- Test design fluencyYou apply equivalence partitioning and decision tables to concrete inputs in real time.
- Metric judgmentYou distinguish between metrics that drive learning and metrics that drive theatre.
- Strategy under constraintYou can produce a defensible plan when the team has half the time and twice the scope.