Introduction to Software Testing. Module Objectives. Introduction to Software Testing Importance of Software Testing Verification and Validation Software Test Lifecycle Testing Process. Goal of testing. The goal of a software tester is: To find bugs To find them as early as possible
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Introduction to Software Testing
Importance of Software Testing
Verification and Validation
Software Test Lifecycle
The goal of a software tester is:
To find bugs
To find them as early as possible
& make sure they get fixed
Testing is a means to:
Provide confidence and information
Even prevent defects
A defect in the software has a root cause, while the effect of defect is
seen as impact by the different stake holders.
Testing is part of overall Quality Assurance – It covers the Quality
Control aspect of ensuring Quality
A fault doesn't necessarily result in a failure, but a failure can only occur if a
fault exists. To avoid a failure you must find the fault.
Software testing may be required for compliance with contractual or legal requirements
When is testing complete?
However for practical reasons it is stopped after considering the
risks involved, time and budget constraints
Why is testing needed
the most common systems that the public had.
charge of more than $400 million to cover the costs of replacing
unexpected setting of a single data bit
the tracking system to be inaccurate after 14 hrs of operation
The tester’s mindset must have the below mentioned attributes
The V-model can be said to have
developed as a result of the evolution of
software testing. Various testing
techniques were defined and various kinds
of testing were clearly separated from
each other which led to the waterfall model
evolving into the V-model. The tests in the
ascending (Validation) hand are derived
directly from their design or requirements
counterparts in the descending
(Verification) hand. The ‘V’ can also stand
for the terms Verification and Validation.