PRINCIPLES OF SOFTWARE

TESTING
1 Non-Functional Testing
NON-FUNCTIONAL TESTING
 Performance testing
 Load testing

 Stress testing

 Security testing

 Usability testing

 Localization testing

2
PERFORMANCE TESTING
 It is used to verify performance behaviors for
application functions under the normal work
conditions.
 It can demonstrate that the system meets
performance criteria.

3
PERFORMANCE TESTING CON’T

 It is performed using a test tool to simulate large

number of users.
 It measures concurrency, throughput and
response time.
 It is conducted to evaluate the compliance of a
system or component with specified performance
requirements

4
LOAD TESTING
 It is the process of putting heavy demand on a
system and measuring its response.
 It is very important for client-server systems
including web application and other business
systems with numerous concurrent users.

5
LOAD TESTING CON’T

 It is considered with measuring the behavior of a

component or system with increasing the load.
 It is testing the web site in order to find out what
point it fails.

6
STRESS TESTING
 It is used to determine the stability of the
system.
 It involves testing beyond normal operational,
often to a breaking point in order to observe the
results.
 Testing at conditions higher than what would be
encountered during normal operation.

7
STRESS TESTING CON’T

 The application is tested against heavy load such

as complex numerical values, large number of
inputs and large number of queries.
 It is better to be prepared for extreme conditions
rather than letting the system/software/web site
crash, when the limit of normal operation is
crossed.

8
SECURITY TESTING
 It is a process to determine that the system
protects data and maintains functionality as
intended.
 Important for payment systems & other
applications which use critical data about users.

9
SECURITY TESTING CON’T

 It informs that the program can restrict access to

authorized users.
 It confirms that the authorized users can access
the functions available to their security level.
 It aims to ensure that the system is accessible
only to those users for which they are intended.

10
USABILITY TESTING
 It is used to evaluate a product by testing it on
users level. It gives direct input on how real users
use the system.
 It aims to determine the extent to which the
software is understood, easy to learn, easy to use
and attractive to users.
 It aims to determine how the software is user
friendly.

11
USABILITY TESTING CON’T

 Goals of usability testing :::

 Performance (how much time? And how many steps?)
 Accuracy (how many mistakes? )
 Recall (how much do you remember after periods of
non-use? )
 Emotional Response (how do you feel after
completing the task? Confident or stressed ?? )

12
LOCALIZATION TESTING
 It is focused on internationalization and
localization aspects of software.
 It is the process of adapting a globalized
application to a particular culture.
 It is making software specially designed for a
specific locality.

13
LOCALIZATION TESTING CON’T

 It includes the translation of the application UI,

content and adapting graphics for a specific
culture.
 The following needs to be considered ::
 Language
 Spelling rules
 Sorting rules
 Date formats

14
15