This document discusses different types of software testing including unit testing, integration testing, system testing, acceptance testing, functional testing, non-functional testing, user interface testing, usability testing, accessibility testing, localization testing, performance testing, load testing, stress testing, compatibility testing, cross-browser testing, security testing, negative testing, re-testing, and regression testing. It provides details on the purpose and goals of each testing type.

1. 1
Yogita J. Patil
Test Lead at Paper Plane Solutions

2. 2
Software testing
It is an investigation conducted to provide
stakeholders with information about the
quality of the product or service under
test.

3. Levels of Software Testing
3

4. Unit Testing
4

5. Unit Testing
5
Here Unit means: The smallest piece of
Software that can be tested in isolation to
verify its behavior.
Unit Testing aims at testing each of the
components that a system is built upon.

6. Faster error detection is one of the major
benefit of it because Unit testing tests
smaller amounts of code making it easy to
narrow down the scope for finding errors.
It’s also simplifies next level of testing i.e.
integration as individual parts of the
program are already tested.

7. Integration Testing

8. Integration Testing
Unit Tested modules work individually, but
they may not work together when integrated.
Integration is dependency between modules
through One module calling other module,
Transfer of data from one module to another.
Purpose of Integration testing is to confirm
that the individually tested units can work
together to deliver the intended functionality.

9. System Testing

10. System Testing
System Testing is conducted on a complete, integrated
system to evaluate the system’s compliance with its
specified features.
Its validate that the system meets its functional and non
functional requirements.

11. AcceptanceTesting

12. Acceptance Testing
Customer or end user of the system perform acceptance
testing based on user requirements specification to
confirm that application is behaving as expected by
them.
The test typically emulate real-world usage of the
application.

13. Acceptance Testing
The idea is that if the software works as
intended and without issues in simulated
environment during acceptance testing, it will
work just the same in production
environment.

14. Types of Software testing

15. 15
Functional Testing
Functional Testing is performed to verify that
software application performs and functions
correctly according to design specification.
Role of functional testing is to validating the
behavior of an application.
Functional Testing Always concentrating on
customers requirements.

16. Non Functional Testing
It focuses on how well an application behaves.
Non functional testing always concentrating on
customer expectations.

17. It is more about testing applications
characteristics like:
 Checking user experience while operating
the Application
Checking operational features of application
Checking security of application

18. 18
User Interface Testing
User Interface Testing determines how user
friendly the application is from look and feel
perspective.
Its include:
 Checking of UI design template from
consistency perspective – font size,
background color, header, footer

19. 19
 Checking of tab sequence
 Placement of controls i.e. Alignment and positioning
 Consistent look of same control throughout an
application

20. 20
Usability Testing
Usability Testing is done to check the ease of
use of an Application.
It also checks for quicker access to the one who
uses application frequently and constantly
Like for web site, is navigation within the web
pages provided and are there home page and
logout links on every page.

21. Accessibility Testing
Accessibility testing ensures that even
physically challenged people can access the
application smoothly and independently.
When text and images are large or
enlargeable, it is easier for users with poor
sight to read and understand the content.

22. Localization Testing
Globalization is a process of application design so that it can
be adapted to different languages and regions without
any change in program code.
It’s a process of adapting a globalized application to a
particular locate

23. Performance Testing
Performance requirements of an application
include
Response time – How fast request is processed
Throughout – Number of transactions processed
by an application per unit of time

24. 24
Its determine how a system performs in terms
of responsiveness to the above requirements
under a particular workload.
Performance testing checks whether an
application provides stipulated output in a
stipulated time.

25. 25
Load Testing
A Load test is conducted to understand the
behavior of the system expected load as per
requirements documents.
Load can be multiple number users accessing
the application concurrently.
For example: A Web application will be used by
a thousand users at a time. It is called load on
application

26. 26
Stress Testing
Stress testing is used to evaluate the ability of an
application to maintain a certain level of
performance effectiveness under unfavorable
conditions.
For example: Testing is conducted by increasing
the number of users beyond the prescribed load
and running several resource applications in a
single computer at the same time.

27. 27
Compatibility Testing
Compatibility Testing tests whether a
product behaves properly when one or
some parts of the configuration are
changed or new configurations need to be
supported.
Testing will include checking application on
 Different Platforms
 Database

28. 28
Cross Browser Testing
Web application are always tested on different
famous browsers as users may use any.
Checking is done for functioning of special
controls and UI.

29. 29
Security Testing
Its determines that an application protects data
and maintains functionality access as intended.
Like Ensures protection against hacking / data
leakage, Unauthorized access to sensitive
information.
Tools: IBM Rational AppScan, HP Web Inspect

30. 30
Negative Testing
Negative Testing can be defined as
Testing with Negative data.
Negative data doesn’t mean testing
Application with negative numbers. It
means testing with invalid Test Data.

31. 31
Invalid test data is a data which the
application is not expecting.
Its necessary to check with invalid test data
as user may accidently input such a data.

32. 32
Re-Testing
After defect is detected and fixed, the software
should be retested to confirm that the original
defect has been successfully removed.
Its also called Confirmation testing.
Previously failed test cases are executed again in
the next cycle to ensure removal of the earlier
existing defect.

33. 33
Regression Testing
It is carried out to determine whether the
changed component has affected the
functionality of the unchanged component.
It is re-execution of related or impacted
functionality test cases.
Previously passed test cases are executed
again in regression testing.

34. 34

35. 35
Case Study 1
Client Requirement: User should redirect to
thank you page after form submission.
Issue Reported by Client: Even after
submitting form successfully user didn’t
redirect on Thank You Page.
At which testing level we missed this
defect?

36. 36
Case Study 2
Client Requirement: On all pages update
button color red to blue.
Which testing types are applicable here?

37. 37
Case Study 3
Client Requirement: Company logo should be
visible on all the pages.
Issue Reported by Client: Company logo is
missing on few pages.
Which testing type we missed here?

38. 38
Case Study 4
Issue Reported by Client: Banner
animation is not working on IE9 browser
and Linux operating System.
Which testing type we missed here?