0% found this document useful (0 votes)
0 views

Week3

The document outlines various software testing methods, including manual and automation testing, and their respective applications. It details different testing approaches such as white box, black box, and grey box testing, along with functional, non-functional, and maintenance testing. The document emphasizes the importance of choosing the right testing method based on the specific needs of the software being tested.

Uploaded by

ar843597
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
0 views

Week3

The document outlines various software testing methods, including manual and automation testing, and their respective applications. It details different testing approaches such as white box, black box, and grey box testing, along with functional, non-functional, and maintenance testing. The document emphasizes the importance of choosing the right testing method based on the specific needs of the software being tested.

Uploaded by

ar843597
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Software

Testing

Instructor: Syed Areeb Jafri


AGENDA

01 Methods of testing

02 Types of testing

03 Testing Approaches, categories

Discussion
#1. Manual Testing
Manual testing is the process of testing the software by hand to learn more about it, to find what is and isn’t working.
This usually includes verifying all the features specified in requirements documents, but often also includes the
testers trying the software with the perspective of their end user’s in mind.
Manual test plans vary from fully scripted test cases, giving testers detailed steps and expected results, through to
high-level guides that steer exploratory testing sessions.

#2. Automation Testing


Automation testing is the process of using automation testing tools to control the execution of tests and compare the
results against expected outcomes and to find the defects.
In this process, testers execute the test scripts and generate the test results automatically by using automation tools.
What Kinds Of Tests To Do When to go for Automation
Manually? in Software Testing?
•Exploratory Testing: This involves a tester 1.Repetitive Tasks: If you have tests that need to be
exploring the application to find bugs that aren’t easy run frequently, automation can save a lot of time and
to detect through automated scripts. It relies on effort. Automated tests can run at any time without
human intuition and creativity. human intervention.
•Usability Testing: This type of testing ensures that 2.Large Datasets: When you need to test with large
the application is user-friendly. Human testers amounts of data, automation can handle it more
evaluate the ease of use, look and feel, and overall efficiently than manual testing.
user experience. 3.Regression Testing: Each time the software changes,
•Ad-hoc Testing: These are unplanned tests without regression tests should be run to make sure existing
any specific approach. Testers randomly test different functionality is not broken. Automation makes regression
parts of the application to find unexpected issues. testing faster and more reliable.
•User Interface (UI) Testing: This involves visually 4.Consistency: Automated tests perform the same
examining the interface to check for visual elements, steps in the exact same way every time, reducing the risk
like layouts, fonts, and colours. Although automation of human error.
tools can assist, human eyes often catch things 5.Performance Testing: For testing the performance
machines might miss. and load capacity of an application, automation is
•Accessibility Testing: Manual testers check if the essential. It can simulate many users interacting with the
application is usable by people with disabilities, system at once.
ensuring adherence to accessibility standards like 6.Complex Scenarios: When you have complex and
WCAG. lengthy test cases, automation can execute them more
quickly and accurately than a manual tester.
Testing Approaches
There are three types of software testing approaches.
#1. White Box Testing
It is also called Glass Box, Clear Box, Structural Testing.
White Box Testing is based on the application’s internal code structure. In white-box testing, an internal perspective
of the system, as well as programming skills, are used to design test cases. This testing is usually done at the unit
level.

#2. Black Box Testing


It is also called Behavioral/Specification-Based/Input-Output Testing.
Black Box Testing is a software testing method in which testers evaluate the functionality of the software under test
without looking at the internal code structure.

#3. Grey Box Testing


Grey box is the combination of both White Box and Black Box Testing.
The tester who works on this type of testing needs to have access to design documents. This helps to create better
test cases in this process.
#1. Functional Testing
In simple words, what the system actually does is functional testing. To verify that each function of the software
application behaves as specified in the requirement document. Testing all the functionalities by providing appropriate
input to verify whether the actual output is matching the expected output or not. It falls within the scope of black-box
testing and the testers need not concern about the source code of the application.

#2. Non-functional Testing


In simple words, how well the system performs is non-functionality testing. Non-functional testing refers to various
aspects of the software such as performance testing, load testing, stress testing, spike testing, endurance testing,
scalability testing, security testing, volume testing, usability testing, compatibility testing, benchmark software
testing, etc., The Main focus is to improve the user experience on how fast the system responds to a request.

#3. Maintenance Testing


Maintenance testing involves regression testing that is performed to validate that a system continues to function
correctly after modifications have been made. These modifications can include updates, enhancements, or bug fixes.
The primary goal of maintenance testing is to ensure that the recent changes have not adversely affected the
existing functionality of the system. It helps in identifying any potential issues that could lead to system downtime or
performance degradation, ultimately ensuring that the software remains reliable and robust throughout its lifecycle.

You might also like