The document outlines the software testing process, emphasizing the importance of validating and verifying software to meet design requirements and user needs. It details various testing methodologies, including unit testing, integration testing, system testing, usability testing, load testing, and acceptance testing, highlighting their specific purposes and procedures. Additionally, it describes acceptance testing types, such as internal and customer acceptance testing, to ensure the software meets expectations before release.

2.  Software testing can be stated as the process of




validating and verifying that a computer
program/application/product:
Meets the requirements that guided its design and
development
Works as expected
Can be implemented with the same characteristics
And satisfies the needs of end users
 The commonly used testing methodologies are unit
testing, integration testing, acceptance testing, and
system testing. Software is subjected to these tests in a
particular order.
www.qaonlinetrainings.com

3. Unit Testing :
The first to be carried out is the unit test. As the name
suggests, this method tests at the object level. Individual
software components are tested for any errors. Accurate
knowledge of the program is needed for this test, as each
module is checked. Thus, this testing is done by the
programmers and not the testers. Test codes are created
to check if the software behaves as it is intended to.
www.qaonlinetrainings.com

4. Integration Testing:
Individual modules that are already subjected to unit
testing are integrated with one another, and are tested for
faults. Such a type of testing highlights interfacing errors.
A 'top-down' approach of integration testing follows the
architectural structure of the system. Another approach
taken is the 'bottom-up' approach, which is conducted
from the bottom of the control flow.
www.qaonlinetrainings.com

5. System Testing:
The software is integrated to the overall product and
tested to show that all requirements are met. In this
testing, the entire system is tested for errors and bugs.
This test is carried out by interfacing hardware and
software components of the entire system, and then
testing it. This testing is listed under the black-box testing
method, where the software is checked for user-expected
working conditions.
www.qaonlinetrainings.com

6.  A) Usability Testing:
Usability testing mainly focuses on the user’s-ease to
use the application, flexibility in handling controls and
ability of the system to meet its objectives
 B) Load Testing:
Load testing is necessary to know that a software
solution will perform under real life loads.
www.qaonlinetrainings.com

7.  C) Regression Testing:
Regression testing involves testing done to make sure
none of the changes made over the course of the
development process have caused new bugs. It also
makes sure no old bugs appear from the addition of new
software modules over time.
 D) Recovery Testing:
Recovery testing is done to demonstrate a software
solution is reliable, trustworthy and can successfully
recoup from possible crashes.
www.qaonlinetrainings.com

8.  E) Migration Testing:
Migration testing is done to ensure that the software can be
moved from older system infrastructures to current
system infrastructures without any issues.
 F) Functional Testing – Also known as functional
completeness testing, functional testing involves trying to
think of any possible missing functions. Testers might
make a list of additional functionalities that a product
could have to improve it during functional testing.
www.qaonlinetrainings.com

9.  G) Hardware/Software Testing:
IBM refers to Hardware/Software testing as “HW/SW
Testing”. This is when the tester focuses his/her attention
on the interactions between the hardware and software
during system testing.
Acceptance testing :
final testing based on specifications of the end-user or
customer, or based on use by end users/ customers over
some limited period of time.
www.qaonlinetrainings.com

10. There are two types of acceptance testing :
 one that is carried out by the members of the
development team, known as internal acceptance testing
(Alpha testing), and the other that is carried out by the
customer, known as external acceptance testing.
 If the testing is carried by the intended customers, it is
termed as customer acceptance testing. In case the test
is performed by the end users of the software, it is known
as user acceptance testing (Beta testing).
www.qaonlinetrainings.com

11. www.qaonlinetrainings.com
609-308-7395
training@qaonlinetrainings.com