2. Example.
1. A clickable button with has name Submet Verification would be check the design
document and correcting the spelling mistake.
Otherwise development team will create button like
So new specification is Submit
A clickable button with name Submit
3. PAN Card
Aadhar Card
3.Paper revaluation
4.Mobile no. verification
5. Document(address) verification
Clik
Click
meena
Mina
3. Verification
Are we building product right?
(i.e. does s/w confirm to it’s specification)
Checks the process of creating the product.
Ensures that “you built it right”
4. Verification
Also called as static testing
Done by manually reading the work
product(document)
Verification testing provides two important benefits:
Presence of defects can be identified close to the point
where they originate
Cost to correct those defects is significantly less when
they detected in dynamic testing(validation)
6. Walkthrough
Informal Process
Led by Author of the work product
Colleagues observe the document and give required
feedback
Author gives explanation if required , and takes down
necessary actions
7. Inspection
It is a Semiformal process
It is done by DOMAIN EXPERTS
It is more detailed than walkthrough
we look for REQUIREMENT TRACEABILITY MATRIX
8. Inspection
Author –owner of the Document
Reader-who read the document
Recorder-who record minute of meeting
Inspector-is a domain expert
Moderator-who schedule the meeting
9. Review
It is a formal or official process
Held at the end of each phase of the project
It is decision making point to gain opinion “is the
phase complete and are we ready to go for next
phase?”i.e. a decision point
This process is carried out by the Managers.
10. Validation
Are we building right product?
(i.e. s/w doing what the user really require)
Checks the end product after creation
Ensures that “you built the right thing”
11. Validation
Validation is also known as Dynamic Testing
It is done by Executing the s/w
The process of evaluating s/w during or at the end of
the development process to determine whether it
satisfied specified requirements
It helps in finding the presence of defects , and not
their location
12. Validation Techniques
Also known as LEVELS OF TESTING:
1.Unit Testing
2.Integration Testing
3.System Testing
4.Acceptance Testing
13. 1.Unit Testing
Unit is smallest piece of independent and executable
code that can perform some functionality or produce
some result as output
Unit Testing is done by programmers to validate if the
unit is working properly
Approach:
White Box Testing
Black Box Testing
Benefits:
Ensures your code does the required task
Simplifies integration between units
14. 2.Integration Testing
Starts at module level when various modules are
integrated with each other to form a system
Integration Testing tests interfaces between modules
Integration Testing becomes easier if Unit Testing is
complete and Interfaces between modules are well-
defined
Integration is done between two similar units of two
different modules
17. When Bottom module is ready and Top Module is not
ready at that time we go for dummy code i.e. driver
Bottom-Up Integration is check by tester
From lower module to Higher Module driver is used
In this first we will test the E, F module with corresponding
B module separately using drivers, and G, H module with
corresponding D module separately using drivers.
Then B module calls the E, F module separately if an error
will there in any module we can easily find out in which
module error will be there.
Then we test the module A with B, D suppose if an error
occurred in B module means there is an error in interface B
and A.
18. Advantages:
We can easily find-out the defects in this approach
Here we no need wait for until all modules ready
Ex:
Suppose in Gmail application, inbox, chat, drafts,
spam, compose all modules are ready but login page is
not ready, then we have to go for dummy code of login
page.
20. From Higher to Lower Module Stub is used
Here Stub is a module it is a temporary replacement
for a called module it gives same output as actual
result.
In above diagram A, C, D modules are developed
modules, but B module is not ready, that’s why here
stub is used in place of ‘B’ module.
Advantages:
We can easily find-out the defects in this approach
Draw Backs:
Needs many stubs
22. In Big-Bang approach we integrated all modules
together and tested
Advantages:
It is suitable for small systems
Draw Backs:
Unable to find from which module defect is raised
Ex:
Suppose if we send the feedback form without
mention the location and center code, head office
members will confuse from which place which
candidate was attended
23. 3.System Testing
Test For functional and non functional requirements
of the system
Test the whole system/product as per scope of release
Tests must be conducted in production environment
This is FINAL phase of testing before release of
software
Final Testing done by tester
Example:
How much RAM is required, which s/w is
required, what is the data size
24. 4.Acceptance Testing
Conducted by customers/users
Forms of user Acceptance Testing
Alpha Testing- Internal
Beta Testing- External
25. Difference between Alpha Testing
& Beta Testing
Alpha Testing (Factory) Beta Testing (Field/Site)
It is always performed by customer at
development environment
It is always performed by customer at
live environment
Not open to market or public Open to market or public
Within organization Outside organization
Comes under both category
White Box
Black Box
Comes under only one category
Black Box
26. BRS
HLD
Integratio
n T
LLD Unit T
SRS
Coding
UAT
System
T
MaintenanceV-Model
P.Tc
P.Tc
P.Tc
P.Tc
E.Tc
E.Tc
verification
validationE.Tc
E.Tc
