This document discusses different levels of software testing including unit testing, integration testing, system testing, and acceptance testing. It provides details on integration testing approaches like big bang testing, top-down testing, bottom-up testing, and hybrid/sandwich testing. Integration tools like Protractor and LDRA are also mentioned. The document explains system testing and the different types of acceptance testing like alpha testing and beta testing.

1. Software Testing
Presented by R R Prianka
Presented by
Dr.PRIANKA R R

2. LEVELS OF TESTING

3. Testing Levels
3
1. Unit Testing
2. Integration /Build Testing
3. System Testing
• Functional Testing
• Performance Testing
4. Acceptance Testing
• Alpha Testing
• Beta Testing

4. A Principal goal is to detect functional and structural
defects in the unit.
At the integration level several components are tested
as group, and tester investigates component interaction.
At the system level the system as a whole is tested and a
principal goal is to evaluate attribute such as ability,
reliability and performance.

5. Integration Testing
• What is Integration Testing?
It is one of the methodology of SDLC where
individual components of Code are tested
validate interactions among different software
system Modules
• It is the process of testing the interface between two
software units or modules.

6. What are the important integration testing
approaches Businesses should know?
Big Bang Testing
Hybrid/Sandwich
Integration Testing
Top/ Down Integration
Testing
Incremental
Testing
Bottom-up
Integration Testing

7. • Combining all the modules once and verifying the
functionality after completion of individual module testing.
Big Bang Approach
Transaction
Module
Reports
Module

8. Transaction
Module
Reports Module
Big Bang Approach

9. • Top down and bottom up are carried out by using dummy modules
known as Stubs and Drivers.
• These Stubs and Drivers are used to stand – in for missing
Components to simulate data communication between modules
Top Down & Bottom Up
Approach

10. Top Down Approach
•In Top Down Approach, testing takes
place from top to bottom.0
•High – level modules are tested first
and then low-level modules and
finally integrating the low- level
modules to the high level to ensure
the system is working as intended.
•Stubs are used as a temporary modules,
if a module is not ready for integration
testing.

11. Bottom Up Approach
• In Bottom Up Approach, testing takes place from bottom to top.
• Lowest – level modules are tested first and then High-level modules
and finally integrating the High- level modules to the Low level to
ensure the system is working as intended.
• Drivers are used as a temporary modules for integration testing.

12. STUBS
Ready for Testing Under Development
STUB
(REGISTRATION PAGE)

13. DRIVERS
Ready for Testing
Under Development
Driver
(LOGIN PAGE)

14. Depth-first integration integrates all modules on a major
control path of the structure as displayed in the following
diagram:

15. Hybrid/Sandwich Integration
Testing
• You can achieve by combining the
bottom –Up and Top-Down Approach.
• As it is using 2 approaches so we can
achieve the benefits of both.
• You don’t need to adopt sandwich
testing for small projects it is suitable
only when a project is based on stub
projects.
• Eg: A big s/w consist on lots of small
s/w which are working together,
• Sandwich testing is the time saving
approach.

16. Steps to perform integration testing
❖ Prepare an effective integration test plan and identify unit
interfaces.
❖Identify critical modules to test on priority
❖Examine the interfaces
❖Demonstrate the integration test conditions

17. What are the important integration tools?
Protractor
LDRA
Rational Integration tester
TESSY

18. System Testing
• System testing is conducted on a complete, integrated system to
evaluate the system's compliance with its specified requirements.
• System testing falls within the scope of black box testing, and as
such, should require no knowledge of the inner design of the code or
logic.
• System testing is most often the final test to verify that the system to
be delivered meets the specification and its purpose.
• System testing should investigate both functional and non-
functional requirements of the testing.

20. System Testing

21. Acceptance Testing:
• After the system test has corrected all or most defects, the system will be
delivered to the user or customer for acceptance testing.
• Acceptance testing is a test conducted to determine if the requirements of a
specification or contract are met prior to its delivery.
• Acceptance testing is basically done by the user or customer although other
stakeholders may be involved as well.

22. steps involved in back-to-back testing
i) Prepare a general-purpose set of test case.
ii) Run one version then another version of the program.
iii) Compare the files produced by the modified and unmodified
program version.

23. Alpha Testing:
• Alpha testing is simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site.
• Alpha testing is often employed for off-the-shelf software as a form of internal
acceptance testing, before the software goes to beta testing.
• This test takes place at the developer’s site.

24. EXAMPLE:

25. Beta Testing:
• It is also known as field testing. It takes place at customer’s site.
• It sends the system to users who install it and use it under real-world working
conditions.
• A beta test is the second phase of software testing in which a sampling of the
intended audience tries the product out.
• Versions of the software, known as beta versions, are released to a limited
audience outside of the programming team.

27. Thank You
27