Verification and

Validation
By K.Satyanarayana
Verification and Validation

Verification Validation
• Verification is also known • Validation is also known
as static testing. as dynamic testing.
• We check whether we are • We check whether the
developing the right developed product is
product or not. right.
• It includes checking
documents, design, codes • It includes testing and
and programs. validating the actual
product.
Verification and Validation
Verification Validation

• It does not include the • It includes the execution

execution of the code. of the code.
• It is a process of checking • It is a process of checking
the work-products (not the software during or at
the final product) of a the end of the
development cycle to development cycle to
decide whether the decide whether the
product meets the software follow the
specified requirements. specified business
requirements.
Verification and Validation
Verification Validation

• Quality • Validation is executed on

assurance comes under software code with the
verification testing. help of testing team.
• In this type of testing, we • In this type of testing, we
can verify that the inputs can validate that the user
follow the outputs or not. accepts the product or
• Verification is done before not.
the validation testing. • After verification testing,
validation testing takes
place.
Verification and Validation
Verification Validation

• In verification testing, we • In the validation testing,

can find the bugs early in we can find those bugs,
the development phase of which are not caught in
the product. the verification process.
Verification Activities
VERIFY REQUIREMENTS AND
OBJECTIVES
VERIFICATION OF OBJECTIVES:
• After gathering requirements, specific objectives are prepared
considering every specification and placed in a document called
software requirement specification.
• In this activity also, two parallel activities are performed by the tester:
1. The tester verifies all the objectives mentioned in SRS. The purpose
of this verification is to ensure that the user’s needs are properly
understood before proceeding with the project.
2. The tester also prepares the System Test Plan which is based on SRS.
Black Box Testing
• Black Box Testing is a software testing method in which the
functionalities of software applications are tested without having
knowledge of internal code structure, implementation details and
internal paths. Black Box Testing mainly focuses on input and
output of software applications and it is entirely based on software
requirements and specifications. It is also known as Behavioral
Testing.
Boundary Value Testing:
• Boundary value testing is focused on the values at boundaries. This
technique determines whether a certain range of values are
acceptable by the system or not. It is very useful in reducing the
number of test cases. It is most suitable for the systems where an
input is within certain ranges.
Example Date(1 to 31)
Invalid partition- Valid partition Lower Invalid partition- Valid partition Upper
Boundary Boundary

Boundary value just Boundary value just Boundary value just Boundary value just
below the boundary above the boundary below the boundary above the boundary

0 1 31 32
Example Username(6 to 10
Characters)
Invalid partition- Valid partition Lower Invalid partition- Valid partition Upper
Boundary Boundary

Boundary value just Boundary value just Boundary value just Boundary value just
below the boundary above the boundary below the boundary above the boundary

5 characters 6 characters 10 characters 11 characters

Floating point values(0.2 to 0.8- one
Decimal Place)
Invalid partition- Valid partition Lower Invalid partition- Valid partition Upper
Boundary Boundary

Boundary value just Boundary value just Boundary value just Boundary value just
below the boundary above the boundary below the boundary above the boundary

0.1 0.2 0.8 0.9

Equivalence Class Testing
• It saves the time in testing and it is also allows you to find more
defects than if you were just using some random input values in your
testing.
• Divide input test data into partitions.
• Test each partition once (the assumption is that any input with in a
partition is equivalent i.e. produces the same output)
Example Date(1 to 31)
Invalid Partition Valid Partition Invalid Partition
0 1 32
-1 2 33
-2 3 34
….. ….. …..
31
Example Username(6 to 10
Characters)
Invalid Partition Valid Partition Invalid Partition
0
0 character
character 6 character
1
1 character
character 7 characters 11 characters
2
2 character
characters 8 characters 12 characters
3
3 character
characters 9 characters ……
4
4 character
characters 10 characters
5
5 character
characters
Example Age(18 to 80 Years Except
60 to 65 Years)
Invalid Partition Valid Partition Invalid Partition Valid Partition Invalid Partition
0
0 Year
Year 18 Years 81 Years
60 Years 66 Years 82 Years
1
1 Year
Year ……. ……. …….
17
17 Years
Years 59 Years …..
65 Years 80 Years
Decision Table Testing
• Decision tables are used in various engineering fields to
represent complex logical relationships. This testing is a
very effective tool in testing the software and its
requirements management.
• The output may be dependent on many input conditions
and decision tables give a tabular view of various
combinations of input conditions and these conditions
are in the form of True(T) and False(F).
• Also, it provides a set of conditions and its
corresponding actions required in the testing.
Decision Table Testing-EMAIL
Example
EMAIL
PASSWORD

Email F T F T
Password F F T T
Expected Error: Please Error: Please Error: Please Login
Result enter email enter Password enter email processed
Decision Table Testing-EMAIL
Example
EMAIL
PASSWORD

Email F T F T
Password F F T T
Expected Error: Please Error: Please Error: Please Login
Result enter email enter Password enter email processed