The document discusses various aspects of software testing, emphasizing its importance in quality assurance and the need to confirm that software meets specified requirements. It outlines a historical perspective on the evolution of testing techniques from debug-oriented to prevention-focused methodologies. The content also highlights that exhaustive testing is impractical and underscores the significance of planned testing processes.

1. SOFTWARE
TESTING
TYPES AND
TECHNIQUES OF
PRESENTATION BY CETPA INFOTECH PVT LTD.

2. TABLE OF CONTENTS
• Software Testing
• Why Software Testing
• Testing Principles
• History of Testing

3. About Software Testing
Software Testing is a process of evaluating a system by manual or automatic
means and verify that it satisfies specified requirements or identify
differences between expected and actual results.
The general aim of testing is to affirm the quality of software systems by
systematically exercising the software in carefully controlled circumstances.--
----Miller

4. It is considered to be the most vulnerable and
sensitive part. There are a bunch of situations in
which the information and details of the users are
stolen and they are used for the benefits.
01
Error Free
Lorem ipsum dolor sit amet, consectetur adipiscing
elit, sed do eiusmod tempor incididunt ut labore et
dolore magna aliqua. Ut enim ad minim
03
Secured
Lorem ipsum dolor sit amet, consectetur adipiscing
elit, sed do eiusmod tempor incididunt ut labore et
dolore magna aliqua. Ut enim ad minim
02
Efficient
Lorem ipsum dolor sit amet, consectetur adipiscing
elit, sed do eiusmod tempor incididunt ut labore et
dolore magna aliqua. Ut enim ad minim
04
Flexible
Why Software Testing ?

5. Made
according to
customer
requirements
Planned long
before Testing
begins
Begin in-the-
small and
progress
towards in-
the-large
Exhaustive
Testing is not
Possible
Testing
Principles

6. History of Testing
Phase I. Before 1956: The Debugging-Oriented Period
Testing was not separated from debugging
Phase II. 1957~78: The Demonstration-Oriented Period
Testing to make sure that the software satisfies its specification
Phase III. 1979~82: The Destruction-Oriented Period
Testing to detect implementation faults
Phase IV. 1983~87: The Evaluation-Oriented Period
Testing to detect faults in requirements and design as well
as in implementation
Phase V. Since 1988: The Prevention-Oriented Period
Testing to prevent faults in requirements, design, and
implementation

7. Contact Us
+91-921-2172-602
www.cetpainfotech.com
D-58, Red FM Road, Sector 2, D Block,
Sector 2, Noida, Uttar Pradesh 201301
query@cetpainfotech.com

8. Thank You