06 | Verification and Validation

Published on Aug 11, 2021 | By Tesvan team

Verification and Validation

 

Verification

Verification in Software Testing is a process of checking documents, design, code, and program in order to check if the software has been built according to the requirements or not. The main goal of verification process is to ensure quality of software application, design, architecture etc. The verification process involves activities like reviews, walk-throughs and inspection.

Validation

Validation in Software Testing is a dynamic mechanism of testing and validating if the software product actually meets the exact needs of the customer or not. The process helps to ensure that the software fulfills the desired use in an appropriate environment. The validation process involves activities like unit testing, integration testing, system testing and user acceptance testing.

Verification VS Validation

                                     Verification                                     Validation
The verifying process includes checking documents, design, code, and programIt is a dynamic mechanism of
testing and validating the actual product
It does not involve executing the codeIt always involves executing the code
Verification uses methods like։
reviews, walkthroughs, inspections,
and desk- checking etc.		It uses methods like Black Box Testing, White Box Testing, and non-functional testing
 Whether the software conforms to
 specification is checked		It checks whether the software meets the requirements and expectations of a customer
It finds bugs early in the development cycleIt can find bugs that the verification process can not catch
Target is application and software
architecture, specification, complete design, high level, and database design, etc.		Target is an actual product
QA team does verification and make sure that the software is as per the requirement
in the SRS document.		With the involvement of the testing team validation is executed on software code.
It comes before validationIt comes after verification

 

 

Useful links
1. Validation vs Verification /article/eng/
2. Difference Between Verification and Validation /article/eng/
3. Validation vs Verification /article/rus/
4. Validation vs Verification /video tutorial/eng/

Next Lessons


07 | Unit testing

Aug 12, 2021

Testing levels There are mainly four Levels of Testing in software testing Unit testingA Unit is a smallest testable portion of system or application which can ...

By Tesvan team

08 | Integration testing

Aug 12, 2021

Integration testing Integration means combining. For Example, in this testing phase, different software modules are combined and tested as a group to make sure ...

By Tesvan team

09 | System testing

Aug 12, 2021

System testing System testing is performed on a complete, integrated system. It allows checking system's compliance as per the requirements. It tests the overal...

By Tesvan team

10 | Acceptance testing

Aug 12, 2021

Acceptance testing Acceptance testing is a test conducted to find if the requirements of a specification or contract are met as per its delivery. Acceptance tes...

By Tesvan team

11 | White-box testing

Aug 13, 2021

White Box Testing White Box Testing is software testing technique in which internal structure, design and coding of software are tested to verify flow of input-...

By Tesvan team

See More

Interesting For You



29 | Agile model

Aug 18, 2021 | By Tesvan team

Agile is a coding practice that follows the rules and principles of agile software development. In this Agile Tutorial, you will learn the fundamentals of Agile...

32 | Kanban methodology

Aug 18, 2021 | By Tesvan team

Kanban methodology Visualize what you do today (workflow): seeing all the items in context of each other can be very informativeLimit the amount of work in prog...