This document introduces software testing. It defines software testing as executing a program to find bugs based on specifications, functionality, and performance. The goals of testing are to find as many faults as possible and ensure the software works properly. Testing should start early in the software development life cycle and continue throughout. Different types of testing exist and test plans must be carefully made and documented.

1. Introduction to
Software Testing

2. What is Software Testing???
It is the process of executing a
program / application with the intent of finding
bugs.
Testing focus on the following
 Specification
 Functionality
 Performance

3. What is our goal during testing?
 Objective 1: find as many faults as
possible
 Objective 2: make you feel confident that
the software works OK

4. Testing Myths
 Myth: Testing is time consuming.
 Reality: During the SDLC phases testing
is never a time consuming process.
However diagnosing and fixing the error
which is identified during proper testing
is a time consuming but productive
activity.

5. Error, Fault & Failure
A person makes an Error
That creates a fault in software
That can cause a failure in
operation

6. When to start testing in SDLC
TestingstartsinRequirement
PhaseandthroughoutSDLC

7. Software Testing Life Cycle

8. Traceability Matrix

9. Entry Criteria
 All test hardware platforms must have
been successfully installed , configured,
and functioning properly.
 Proper test data is available.
 Approved business requirements

10. Exit Criteria
 All Test plans have been run atleast
once
 All items in scope was tested
 No high priority or severe bugs are left
outstanding.
 Sign-off on testing was obtained

11. Types of Testing

12. Summary
 Do test as early as possible
 Test activities must be carefully planned,
controlled and documented.
 No single reliability model performs best
consistently
 Testing is a continuous process