Slides about different types of testing including verification, validation and calibration. It is not same as regular PPT. I don't have conclusion part, because there's not always a hero in the story.

1. Different types
oftesting
@sidbelbase
1

2. Overview
• Introductionto testing
• Importance of testing in SDLC
• Testing life cycle
• Types of testing
• Verification,Validation and Calibration
2

3. Introduction to software testing
3

4. Software Testing
Software testing is a process used to identify the correctness, completeness and quality of
any developedcomputer software.
It is the process of executing a program/application under positive and negative conditions
by manual or automatedmeans . It mainly checks for:
“Does it do what it suppose to do and do what it needs to do.”
4

5. Why software testing?
• Uncover as many as bugs as possible in a given product.
• Demonstrate a given software product matching its environment
and hardware specifications.
• Validate the quality of a software testing using the minimum cost
and efforts.
• Generate high quality test cases, perform effective tests, and
issue correct and helpful problem reports.
5

6. Who should test?
Developer Independent tester
They have to understand the system. They must learn the system.
They will test everything gently. They might be able to break things.
They are driven by the deadline. They are driven by the quality.
6

7. Testing in SDLC
7

8. Types of testing in SDLC
The tester needs to put some extra efforts to pull out the most of the defects in the
system introduced in our previous phases of SDLC i.e. Requirement Phase, Design Phase
& Coding Phase. Here are the tests we do at this testing phase:
Component Testing: In this stage all components are tested and make sure that all
componentsare working fine.
Requirements Testing: In this stage we test entire system against the requirement. The
main objective behind this stage is to make sure that system is acting as mentioned in the
requirement.
Acceptance Testing: Here we present complete system to the business team where they
test the system with business perspective.
8

9. Testing life cycle Project
Initiation
Summary
Reports
Analysis
Regression
Test
Report
Defects
Execute
Test Cases
Design Test
Cases
Test Plan
System
Study
1. Requirement Analysis:
• Project Initiation
• System Study
2. Test Plan
3. Test Design
4. Test Environment Setup
5. Test Execution
• Report Defects
• Regression Test
6. Test Closure
• Analysis
• Summary Reports
9

10. Types of testing
10

11. Unit testing
1. Test each module individually
2. Follows a white box testing (logic of the program)
3. Done by developers
11

12. Integration testing
After completing modules development, programmers connect the
modules with respect to the design. It works to expose defects in the
interfaces and interaction between modules.
12

13. System testing
After completing unit and integration testing through white box testing
techniques development team release an exe build (all integrated
module) to perform black box testing, which are as follows:
• Usability testing
• Functional testing
• Performance testing
• Security testing
13

14. 1. Usability testing
During this test, testing team concentrates on the user friendliness or build
interfaces. It consists of following sub tests:
• User interface test: ease of use (screens should be understandable to operate)
• Look & feel: attractiveness
• Speed in interface: number of task to complete
• Manual support test: context sensitiveness of user manual.
14

15. 2. Functional testing
• It is the process of checking the behavior of the application.
• It is geared to functional requirements of an application.
• To check the correctness of outputs.
• Data validation and integration i.e. input are correct or not.
15

16. 3. Performance testing
• Load testing - also known as scalability testing. During this test, engineers
execute application build under customer expected configuration and load
to estimate performance.
• Stress testing- during this test, engineers estimates the peak load. To find
out the maximum number of users for execution of out application user
customer expected configuration to estimate peak load.
• Data volume testing- testing team conducts this test to find the maximum
limit of data volume of your application.
16

17. 4. Security testing
Testing how well the system protects against
unauthorized internal or external access or willful
damages that may require sophistical testing techniques.
17

18. Verification, Validation & Calibration
18

19. Validation: Is its system function
satisfactory?
Validation is used to give information regarding the accuracy or inaccuracy
of the product. It is a check to confirm that the product fits the
specifications required for that particular use. It is the process of
confirming that it meets user requirements and can be used for a specific
purpose.
19

20. Verification: Is it working correctly?
Verification is the process of confirming that software meets its specification,
done through inspections & walkthroughs. It is also used to identify defects in
the product early in the life cycle. This is the process of checking against a
standard or reference to confirm that the product fits the broad and specific
specs provided by its manufacturer.
20

21. Calibration: Is it accurate?
Calibration is a process that provides corrections which makes a product
accurate. Calibration services are based on the process of comparison
with a reference or standard in order to give set corrections and/or
uncertainties characteristic of the product that is being calibrated. The
results of the calibration process may be then used in the adjustment of
the software.
21

22. THANK YOU!
22