Scribd
Upload
1 views

Module 3 System Testing types

The document outlines the types of system testing, dividing it into functional and non-functional testing. It details various functional testing types such as behavioral coverage, input domain testing, error handling coverage, backend coverage, calculation base coverage, and globalization testing. Non-functional testing types include recovery testing, compatibility testing, intersystem testing, parallel testing, and installation testing, along with distinctions between performance, load, and stress testing.

Uploaded by

Harshal Khairnar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
1 views

Module 3 System Testing types

The document outlines the types of system testing, dividing it into functional and non-functional testing. It details various functional testing types such as behavioral coverage, input domain testing, error handling coverage, backend coverage, calculation base coverage, and globalization testing. Non-functional testing types include recovery testing, compatibility testing, intersystem testing, parallel testing, and installation testing, along with distinctions between performance, load, and stress testing.

Uploaded by

Harshal Khairnar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Module 3

SYSTEM TESTING TYPES


System testing is divided into two parts
Functional testing talks about how your software should work whereas non-
functional testing mainly focus on performance of your software the load it
can take how reliable it is.

1. Functional testing
2. Non-functional testing

Types of functional testing

1. Behavioral coverage
In Behavioral coverage this we check property and behavior of
object

Ex. 1 text box


Property –accept user input
Behavior –focus or not focus

Manual Testing Notes by Rohit Sir


Ex. 2 check box
Property of the check box:-check box do tick when user click
Behavior of the check box:-check box check or uncheck

2. INPUT DOMAIN TESTING


In input domain testing we checks type and size of input
Type’s means –Data types string, integer, char etc.
Size means – length or size of data. Ex.mobile number ==10 digit
In input domain coverage we have to maintain boundary value analysis and
equivalence class partitioning

Manual Testing Notes by Rohit Sir


3. ERROR HANDLING COVERAGE

• Error handling coverage means whether system showing error message or


not
• If in customer requirement mobile number should be accept 10 digit then
developer develop build according to customer requirement
• If customer entre 2 digit and click on ok button then system should
highlight text box with red color and error message is please entre 10 digit
mobile number
• So this is process of validation whether system show error message or not

4. BACKEND COVERAGE

What is Backend Testing?


Backend Testing is a testing method that checks the server side or database
of web applications or a software. The purpose of backend testing is to test
the application layer or database layer to ensure that the web application or
software is free from database defects like deadlock, data corruption or data
loss.

Backend testing is also known as Database Testing. The data entered in the
front end will be stored in the back-end database.

Manual Testing Notes by Rohit Sir


In back end coverage developer / tester check whether the entered information
from user get stored in database or not

5. Calculation base coverage

Calculation base coverage checks arithmetic operation


Arithmetic operation includes addition, subtraction, multiplication, division
Eg . if we add 1 thing and its of 100 rs then total is 100.
If we added 2 things total should 200.

Manual Testing Notes by Rohit Sir


6. Globalization Testing:
Globalization testing is to ensure that application can function in any culture or
local called globalization testing

NON FUNCTIONAL TESTING


1. Recovery Testing

Aim: process of checking whether system is able to recover from abnormal


situation to normal situation
Ex. when we accessing Google page and sudden internet connection loss then
Google shows that you are offline and whenever connection resume page which
we are accessing shown by Google
Compatibility testing

Aim: its process of checking whether the build is compatible with user expected
platform or not

Manual Testing Notes by Rohit Sir


Operating system or browser

Compatibility testing has two categories

1. software compatibility
Types of compatibility
Forward compatibility----build is ok but browser/os does not work properly
Backward compatibility--if browse/ os is ok but build is not working properly

Browser compatibility
1. Cross browser compatibility—testing on different browser (chrome, Firefox, ie)
2. Version comparison - e.g. chrome 1.6,1.8 etc. .

2. Intersystem testing
Its process of checking whether our application is able to share the resources
With other application.
Eg suppose we have to make payment to jio from paytm then paytm fetch data
from gio application his data sharing is checked in intersystem
Data communication with xml

3. Parallel Testing
Parallel testing is testing multiple applications or components of the application
concurrently, to reduce the test time. Parallel tests consist of two or more parts that check

Manual Testing Notes by Rohit Sir


separate parts or features of an application. These parts are executed on individual
computers simultaneously. Parallel testing allows reducing the test time significantly and
increase the testing efficiency.

4. Installation Testing/Uninstallation
Process of checking installation of our build with existing software into a user
expected platform.

5. Differences between Performance, Load, and Stress Testing

• Performance testing includes both load testing and stress testing.


Performance testing is concerned with evaluating the overall system’s
performance, response time, and stability.

• Load testing is a technique that verifies whether the application can


handle the expected load.

• A testing engineer uses stress testing to find the breaking point of


application.

Manual Testing Notes by Rohit Sir

You might also like