Software Testing

-Presented BY
Vikas Sonavane (07030141077)
Anamika (07030141079)
Raviraj Desai (07030141081)
Sumit Kurolya (07030141084)
B.H.Divya.Rao (07030141086)
Agenda
 Introduction
 Need Of Testing
 Testing Life Cycle
 V-Model
 Levels Of Testing
 Testing Methodologies
 Levels Of Testing
 Documents for Testing
 Tools for Testing
Introduction
 Software testing is a process to uncover errors
and test the quality to give information about
the product under test.
 Testing compares the state and behavior of
the system against a specification
 Testing is a set of activities that can be
planned in advance and conducted
systematically
Need of testing

 Find as many problems as possible

 Verification
 Ambiguous requirements specifications
 Validation
 Absence of standardized methods of
programming
Testing Life Cycle
1. Creation of a Test Plan
2. Creation of a Test Suite
3. Creation of a Requirements vs. Tests matrix
4. Test Case Writing :
a. Creation of Unit level test cases
b. Creation of Module / Integration level test cases.
5. Test Case Execution :
a. Execution of Unit Level Test cases
b. Execution of Module / Integration level test cases
6. Creation of defect report
7. Regression Testing ( i.e. second round of testing after
the defects have been corrected)
V-Model
Levels Of Testing

 Unit level testing

 Module level testing
 Integration testing
 System testing
Unit Testing
 Unit is the smallest component of the software .
 Unit testing focuses on verification of the
smallest unit of software design.
 The unit level tests are for :
 Valid values
 Invalid values
 Accuracy of calculations
 Navigation within the unit
 Validation and error messages
Module testing
A module can be a collection of units for the
same sub-division. e.g. for a banking software
there can be a module for Saving Accounts
 In a module level testing, the functioning of the
module is tested. The connections between
various units of the module are checked.
Integration Testing
 Inthe Integration Testing, the connections
between various modules are tested.

 Though the number of test cases for the

Integration Level testing may be less, these
test determine whether the software is working
satisfactorily.
System Testing
 After the Integration Level testing is over, the
System Testing is carried out.
 The System Testing is carried out against the
Functional Specifications
 It has a destructive approach and it is the final
testing before carrying out the Acceptance
Testing or the User Acceptance Testing.
Testing methodologies

 Black Box Testing

 White Box Testing
 Grey Box Testing
 Ad-hoc Testing
 Top-down/Bottom-up Testing
 Alpha and Beta Testing
Black Box Testing
 In this method of testing, the source code is
not examined. Instead, test cases are written
on the basis of functional requirements and
the results of the test cases are examined to
determine whether the software is working
satisfactorily.
White Box Testing
 In this method of testing, the source code is
examined line by line to ensure that the
functional requirements are being met.

 Thiscan be a lengthy process if the source

code contains thousands of lines of code
Grey Box Testing
 Grey box testing is a software testing technique
that uses a combination of black box testing and
white box testing.
 A limited number of test cases are used to the
internal workings of the software under test. In the
remaining part of the grey box testing, a black box
approach is taken in applying inputs to the
software under test and observing the outputs.
Ad-hoc Testing

A testing phase where the tester tries to

'break' the system by randomly trying the
system's functionality.

 This is the least formal method of

testing.
Top-down/Bottom-up Testing
Alpha-Beta Testing
 Alpha testing is simulated or actual operational
testing by potential users/customers or an
independent test team at the developers’ site.
 In Beta testing the beta version software is
released to groups of people so that further testing
can ensure the product has few faults or bugs.
Types Of Testing

 User Acceptance Testing

 Stress Testing
 Load Testing
Document for Testing

 Test Plan (what to test)

 Test specification (how to test)
 Test result analysis and report (what are
the results)
Tool for Testing

 Quicktest Professional
 Win Runner
 Load Runner
References

 Roger Pressman, Software

Engineering ,6th Edition, McGraw Hill;
 www.softwaretestingandbusiness.com
 www.testinginformation.com
 www.UNCC-IESLecture16%20-%20%softwar
;
 www.wikipedia.com
Thank you!!!!!!!