Software Testing

Software Testing - Verification vs. Validation

What Is Validation?
Validation is the process of evaluate the final product to check whether the software meets the business needs.

Validation represents dynamic testing techniques.
What Is Verification?
Verification is a process of evaluating the intermediary work products of a software development lifecycle to check if we are in the right track of creating the final product.

What Is the Differences between Verification and Validation in Software Testing?

Verifications -
1.      Execution of code is not comes under verification.
2.      Verification uses methods like reviews, walkthroughs, inspections, and desk- checking.
3.      Verification finds bugs early in the development cycle.
4.      Verification comes before validations.

There are four types of verification -
Component Testing - This testing verify a software element (unit).
Integration Testing - This testing verify if the units work together.
System Testing - This testing verifies and meets the system requirements.
Acceptance Testing - This testing verify the system satisfies acceptance criteria.

Validation -
1.      Execution of code is comes under the validation.
2.      Validation uses methods like Black Box Testing, White Box Testing and non-functional testing.
3.      Validation can find bugs, errors or defects that the verification process cannot catch.
4.      Validation comes after verifications.


Anil Singh is an author, tech blogger, and software programmer. Book writing, tech blogging is something do extra and Anil love doing it. For more detail, kindly refer to this link..

My Tech Blog -
My Books - Book 1 and Book 2

Software Testing - Verification vs. Validation Software Testing - Verification vs. Validation Reviewed by Anil Singh on 2:56 AM Rating: (5) Powered by Blogger.