MANUAL TESTING

MODULE 3
 Positive testing
• Performing the testing on the application with positive data or valid data is called positive testing.
• It checks whether an application behaves as expected with positive inputs
• For example : Enter only numbers

99999

Negative testing
• Performing the testing on the application with negative data or invalid data is called negative testing.
• It checks whether an application behaves as expected with the negative inputs
• For example : Enter only numbers

abcdef
End to End Testing

Testing the overall functionalities of the system including the data integration among all the modules is called
end to end testing .
 Security testing
• validating the security of the application with respect to authentication and authorization is called security
testing

Authentication
• verifying whether the application is accepting the valid user and rejecting the invalid user or not is called
authentication.

Authorization
• Verifying whether the application is providing the right permission to right users or not is called
authorization.
Example: Both agent and customer is able to login the online ticket booking application.
Agent can book maximum 20 tickets and customer book maximum 5 tickets.
 Exploratory testing

• Performing testing on the software application parallelly be learning domain knowledge is called
exploratory testing.
• we are performing exploratory testing in project only when the resource is shifting from one domain to
another domain.
 Ad-Hoc Testing

• Testing application randomly without any test cases or any business requirement document
• Testers should have the knowledge of application even though he doesn’t have requirements /test cases
• Ad-Hoc testing is an informal testing type with an aim to break the system

• This testing is usually unplanned activity

 Performance testing

Performance requirements of an application include :

• Response time- How fast a request is processed/served.
• Throughput- Number of transactions processed by an application per unit of time.

Performance testing determines 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.

It is carried out after functional testing.

Types of Performance testing

Load testing :
• A load test is conducted to understand the behaviour of the system under a specific expected load as per
requirements document .
• Load can be multiple number users accessing the application concurrently.
Example: Web application will be used by a thousand users at a time. It is called load on the application.
600 users log in , browse and then log off .
250 users log in , add items to cart, check out log off .
150 users jus log in without any subsequent activity.
Endurance testing :
• Endurance testing determines whether a system can sustain a continuous expected load for a longer
duration of time.
• Predefined load is applies for a longer period of time and an application performance is checked.
Example: check the above web application flooded with a thousand users throughout the day.
 Stress testing :
Stress testing is used to evaluate the ability of an application to maintain a certain level of performance
effectiveness under unfavourable conditions. unfavourable conditions include
• Overloading of existing resources with the excess jobs .
• Application of load beyond the specified limits .
Example: Testing is conducted by increasing the number of users beyond the prescribed load and

running several resource-intensive applications in a single computer at the same time.

 Monkey Testing

• Performing testing on the application randomly (without any sequence) is called Random testing.
• We are performing random testing only when we don’t have sufficient time to complete the testing in a
project.
• Suitable for Gaming applications .
 Localization Testing

• Performing the testing on application in different local languages like Telugu, Tamil, Kannada etc. is called
localization testing.
• Localized product only supports the specific kind of language and is usable only in specific region .
Note: localization testing is also called as lion testing
 User Interface Testing

UI comprises of controls like Textbox, Text area, Radio buttons, Dropdown lists, Checkboxes, etc.

UI testing determines how user friendly the application is from look and feel perspective .
Checklist for UI testing :

• Checking of UI design template from consistency and appropriateness perspective – font size, background
and foreground colour schemes, frames, header, footer .
• Checking of Tab sequence
• Placement of controls i.e. Alignment and positioning

• Consistent look of same control throughout an application .

• Screen resizing options
Usability Testing

Usability testing is done to check the ease of use of application

Usability testing caters to how easy it is for a new user to carry out the basic tasks of the application

It also checks for quicker access to the one who uses application frequently and constantly.

Checklist for usability testing :

Is the user guided within the application ?

Are proper error message and adequate help provided to the user on incorrect steps?
Do new users understand the application usage quickly ??
Configuration Testing

• Configuration means minimum requirement of following components for running the application .
• When an application is developed , it is designed to work for a particular configuration.

• Configuration testing is done to assess an application’s behaviour and performance on the range of hardware
and software configurations for which it is designed

Hardware : RAM, Hard Disk, Type of Monitor, Microprocessor

Other peripheral Devices : Printer , Mouse
Software : Operating system i.e. , Windows, Linux, etc other pre requisite software .
Compatibility Testing

• Test application for the configuration for which it is not designed and check its compatibility.
• Cross-browser compatibility testing
Web applications are always tested on different famous browsers as users may use any.
Checking is done for functioning of special controls and UI
• Tools :

Browser shots, Browsera, Browser Cam.

 Installation Testing

• Installation testing is done after system testing

• Needs proper documented installation procedure
• Identifies different ways in which installation procedure may cause errors .
 Internalization testing /Globalisation testing

• Performing the testing on application in different international languages like French, Spanish, Chinese
etc. is called internationalization testing.
Note: Internationalization testing is also called as i18n testing
For example : PayPal
THANK YOU !!!!