Verification Validation

Evaluates the intermediary Evaluates the final

products to check whether it product to check
meets the specific whether it meets the
requirements of the business needs.
particular phase

Checks whether the product It determines whether

is built as per the specified the software is fit for
requirement and design use and satisfy the
specification. business need.

Checks “Are we building the Checks “Are we building

product right”? the right product”?

This is done without Is done with executing

executing the software the software

Involves all the static testing Includes all the dynamic

techniques testing techniques.

Examples includes reviews, Example includes all

inspection and walkthrough types of testing like
smoke, regression,
functional, systems and
UAT

What is Verification Testing ?

Verification is the process of evaluating work-products of a development
phase to determine whether they meet the specified requirements.

verification ensures that the product is built according to the requirements

and design specifications. It also answers to the question, Are we building
the product right?

Verification Testing - Workflow:

verification testing can be best demonstrated using V-Model. The artefacts
such as test Plans, requirement specification, design, code and test cases
are evaluated.
Activities:
 Reviews: A review is a systematic examination of a document by one or more people
with the main aim of finding and removing errors early in the software development life
cycle. Reviews are used to verify documents such as requirements, system designs,
code, test plans and test cases.

 Walkthroughs: Walkthrough is there for both Testing and Coding. Walkthrough for
testing means brief review of documents, Testcases, Test script etc. Walkthrough for
Coding means review the coding for whether the Developer follows the Coding standards
or not.
 Inspection: Inspection is usually led by a trained moderator, who is not the author.
Moderator's role is to do a peer examination of a document. Inspection is most formal
and driven by checklists and rules. This review process makes use of entry and exit
criteria. Inspection report is prepared and shared with the author for appropriate
actions.

Validation Testing
Validation Testing ensures that the product actually meets the client's
needs. It can also be defined as to demonstrate that the product fulfills its
intended use when deployed on appropriate environment.

It answers to the question, Are we building the right product?

Validation Testing - Workflow:

Validation testing can be best demonstrated using V-Model. The
Software/product under test is evaluated during this type of testing.

Activities:
 Unit Testing: It is basically done by the developers to make sure that their code is
working fine and meet the user specifications. They test their piece of code which they
have written like classes, functions, interfaces and procedures. Unit testing, a testing
technique using which individual modules are tested to determine if there are any issues
by the developer himself. It is concerned with functional correctness of the standalone
modules. The main aim is to isolate each unit of the system to identify, analyze and fix
the defects.

Unit Testing Techniques:

 Black Box Testing - Using which the user interface, input and output are tested.

 White Box Testing - used to test each one of those functions behaviour is tested.

 Gray Box Testing - Used to execute tests, risks and assessment methods.

Integration Testing: Upon completion of unit testing, the units or modules are to be
integrated which gives raise to integration testing. The purpose of integration testing is to verify
the functional, performance, and reliability between the modules that are integrated.
Integration Testing Techniques:
 Big-Bang Integration: Big Bang Integration Testing is an integration testing strategy
wherein all units are linked at once, resulting in a complete system. When this type of
testing strategy is adopted, it is difficult to isolate any errors found, because attention is
not paid to verifying the interfaces across individual units.

Top Down Integration: Top-down integration testing is an integration

testing technique used in order to simulate the behaviour of the lower-level
modules that are not yet integrated. Stubs are the modules that act as
temporary replacement for a called module and give the same output as
that of the actual product.

The replacement for the 'called' modules is known as 'Stubs' and is also
used when the software needs to interact with an external system.

Stub - Flow Diagram:

The above diagrams clearly states that Modules 1, 2 and 3 are available for
integration, whereas, below modules are still under development that
cannot be integrated at this point of time. Hence, Stubs are used to test the
modules.