Verification and Validation in Testing
Verification and Validation is also referred as V&V in short.
Verification refers to the set of activities that ensure that software correctly implements a specific function. In other words, Verification puts the question “Are we building the product right?”.
Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements. In other words, Validation puts the question “Are we building the right product?”.
Validation testing starts after integration testing has been done. It acts as a final series of software tests. Validation succeeds when the software functions in a manner that can be reasonably expected by the customer. Software must function according to the requirement specification mentioned in the SRS (Software Requirements Specification) document. The specification contains a section called Validation Criteria.
Validation Test Criteria:
Software validation ensures conformity with requirements. It is achieved by a series of black box tests. Testing consists of two parts:
• Test Plan: Test plan includes all classes of tests which must be performed.
• Test Procedure: It specifies specific test cases that will be used to demonstrate conformity with requirements.
Test plan and test procedure ensure that the software meets the functional requirements, performance requirements and documentation correctness.
After the validation testing has been done, one of the two scenarios given below can occur:
I. The function or performance characteristics conform to specification and are accepted, or
II. A deviation from specification is uncovered and a deficiency list is created.
However, error at this stage is rarely corrected before scheduled completion time. And hence, it is often negotiated with customers.