Introduction to software testing

S/W testing is a process of executing with the

intention of finding errors in code.
It is the process of exercising or evaluating
the SYST or SYST component.
And to identify difference between expected
and actual results.
The objective of testing may be to detect as
many errors possible and to ensure proper
functionality before the system is delivered to
customer.
S/W testing of a product begins after the
development of the program units and continues

Debugging
Debugging is the process of locating & correcting the defects in
the s/w.
The process of debugging involves following steps:1. Test case execution
2. Fault locations
3. Fault correction
4. Regression testing
Test
cases

Test case
Regression
execution
testing

Fault

Fault

location

correction

The debugging process

Testing process
The testing process consists of 5
stages are:Unit testing
Module
testing
Sub system
testing
System
testing
Acceptance
Testing

Test planning
Test plan is a document with a complex set of test cases along with
other information about testing.
Important components of s/w test plans are:
1. Testing process
2. Requirement traceability
3. Items to be tested
4. Testing schedule
5. Test recording procedure
6. H/W & S/W requirements
7. Constraints

Testing strategies

Testing strategies are:

1. Top-down testing
2. Bottom-up testing
3. Thread testing
4. Stress testing
5. Back to back testing

Testing Methods

Black-Box Testing
White-Box Testing
Alpha Testing
Beta Testing
Clean Room Testing

Black-Box Testing
Black-box testing treats the software as a
"black box", examining functionality without
any knowledge of internal implementation.
The tester is only aware of what the software
is supposed to do, not how it does it. This type
of testing is based entirely on the software
requirements and specifications. It aims at
finding cases in which the software does not
behave according to its specifications or
requirements.

White-Box Testing
White-box testing tests internal structures
or workings of a program, as opposed to the
functionality exposed to the end-user. In
white-box testing an internal perspective of
the system, as well as programming skills,
are used to design test cases. The tester
chooses inputs to exercise paths through the
code and determine the appropriate
outputs.

Alpha Testing
In this type of testing, the users are invited at
the development center where they use the
application and the developers note every
particular input or action carried out by the
user. Any type of abnormal behavior of the
system is noted and rectified by the
developers.

Beta Testing
Beta testing is the process of subjecting a
product to testing by real customers in their
real environments prior to its release. It adds a
key dimension to quality testing given the
unscripted use and wide variety of
environments that can't be replicated in a lab
setting.

Clean Room Testing

The Clean Room for software engineering
was first proposed by Mill and his
colleagues at IBM in 1980. It reflects the
idea used in chip production to keep faults
minimum. It enhances the quality of
software. It is based on two principles:
Produce zero faults
Uncover errors in specification rather than
in unit testing.

Conclusion
Testing is more than just debugging.
Testing is not only used to locate defects
and correct them. It is also used in
validation, verification process, and
reliability measurement. Testing is
expensive. Automation is a good way to
cut down cost and time.