INTRODUCTION

» Name : Eman
Fatima Ijaz
» Degree : ADS CS
(4th)
» Subject : Software
Engineering
» Topic: Software
 SOFTWARE TESTING

 Introduction
 Levels Of Testing
 Categories
1.Functional Testing
2.Non-functional Testing
 SOFTWARE TESTING
• WHY WE NEED TO TEST ?
In 1994, China Airlines Airbus A300 crashed due to a software bug
killing 264 people .In 1999, a software bug caused the failure of a
$1.2 billion military satellite launch. In 2015, a software bug in
fighter plane F-35 resulted in making it unable to detect targets
correctly.
• Software testing :
Software testing is a process to check the functionality of a software ,to find
whether the developed software meets the requirements of Users. Testing
comes after implementation and it’s the Fourth stage of SDLC ensures that
developed software works correctly and is free of bugs before deployment.
Case Study:
The NASA Mars Climate Orbiter was a $125 million spacecraft launched
in 1998. It was designed to study the Martian atmosphere changes but as
the spacecraft entered too low an orbit around .It burned up in the
Martian atmosphere.
➤ Causes:
1.Orbitor lacks of Integration testing, however unit-testing of individual
modules may have passed.But no integration tests verified data flow between
systems.
2.Interface Testing was also Missing.
3.There was no automatic unit conversion or data validation check
between the components.
SOFTWARE 1.FUNCTIONAL Unit Testing

TESTING TESTING
System testing

Integration testing

2. NON Development Testing

FUNCTIONAL
Performance Testing
TESTING
Regression Testing

Stress Testing
LEVELS OF TESTING :

1.UNIT 2.INTEGRATED 3.SYTEM 4.ACCEPTANCE

TESTING TESTING TESTING TESTING
 1) UNIT TESTING :
Unit testing focuses on testing individual functions, methods, or modules
of a program in isolation. It ensures that each piece of the code performs as
expected independently. The developers perform this testing using tools like
JUnit for Java ,PyTest for Python and Google Test for C++.

FEATURES :

•It provides fast feedback and Detects regressions early.

•Unit testing Encourages modular code.
•Drawback is that it does’nt test interactions between
components(modules).
•Doesn’t catch integration bugs or errors .
EXAMPLES OF UNIT TESTING :
EXAMPLE UNIT BASE TESTING EXPLANATION

Test various input to ensure

Calculator App add(a, b) function
correct addition logic.

Ensure correct/incorrect
ATM Machine validatePIN() PINs are processed
accurately.
Verify correct identification of
Web App validateEmail() function
valid/invalid email formats.
Test scoring mechanism in
Game Engine updateScore() method isolation from game UI or
logic.
 2) INTEGRATION TESTING :
Integration Testing ensures that different modules or services work together
correctly in a software. It focuses on interfaces, data flow, and interaction
between components.
EXAMPLE :
•A login module sends data to a user profile module. Integration testing verifies that
after login, the correct profile is loaded.
FEATURES :
•Detects interface issues (e.g., Data mismatch, incorrect API calls)
•Ensures proper flow of data and control
•Can be complex when many modules are involved
•Needs good planning of stubs and drivers
EXAMPLES :
Modules Involvement What’s Tested Description

Credential Ensure login screen properly

Login ↔ Database
validation communicates with the user database.

Check if data entered in app (e.g., a fitness

Mobile App ↔ Backend API Data sync
tracker) syncs correctly with the server.

Verify that balance shown matches bank

ATM ↔ Bank Server Balance inquiry
records after transactions.

Ensure new messages trigger notifications

Watsapp ↔ Notification System Real-time alerts
correctly.
3)SYSTEM TESTING :
System testing is performed after Integration Testing and before Acceptance
testing. In software development it evaluates the entire software product to
ensure it meets the specified requirements. It focuses on how different
components work together as a whole. It treats the system as a black box.
The Quality Assurance (QA) team /testers performs System Testing using
tools like Selenium , Appium and Postman.
• Examples:
flow : sign-up → order food → payment → delivery
Food Delivery App
tracking.
Register user → search book → issue book → send due
Library Management System
date alerts.
Flow : location tracking → ride matching → fare
Ride Sharing App
calculation → payment → rating driver.
FEATURES OF TESTING

• System testing validates the whole product

• It uncovers system-level bugs
• It can tests real-world scenarios
• System testing is more expensive and time-consuming
• It’s harder to isolate the root cause of a failure
 4)ACCEPTANCE TESTING :
Acceptance testing ensures the software meets business requirements and
is acceptable to the end-users or clients.
This testing is performed by end users ,Customers ,stakeholders, and also by
testers .The testing is done by Feedback collection tools like Instabug ,
SurveyMonkey and also manually

Features :
•Ensures the product meets end-user needs
•Detects usability issues
•Acts as a final gate before production
•May not cover all scenarios
•Feedback can be subjective
 TYPES :
Type Function
Alpha Testing Performed in-house by internal staff/users before release.
Released to a limited number of users(external) outside the
Beta Testing
company to gather feedback.

EXAMPLES :
1) Mobile Application :
A bank develop an App and send it to 100 people (beta testers) before sending it to its
Customers.
2)Online Shopping Apps :
When a user wants to purchase anyting Online then he is firstly Login into the
App.Then he provide bank details.Here , Acceptance works in Beta testing
method ,the end user ( customers ) data should be protected.The transactions must
be carried successfully.The website/App should not crash and it should send
confirmation SMS or an email.
VERIFICATION AND VALIDATION (V&V):
Verification focuses on internal process quality of Software modules .The common methods for
verification are :
• Code Reviews: Peers checks code for logic errors or deviations.
• Walkthroughs: Present code/design to reviewers.
• Static Analysis: Use tools like SonarQube to detect code smells or vulnerabilities.
• Example: During the design phase of a hospital management system, architects ensure the
database schema meets all data flow and privacy requirements.
Validation of Software focuses on meeting the customer's requirements effiently.The Methods:
• Functional Testing: Validates specific features.
• Usability Testing: Tests how user-friendly the product is.
• Performance Testing: Ensures the app runs efficiently under load.
 DIFFERENCE B/W VERIFICATION & VALIDATION

It includes checking documents, designs, It includes testing and validating the

 Focus codes, and programs. actual product.

 Methods Methods used in validation are

Methods used in verification are reviews,
Black Box Testing, White Box Testing
walkthroughs, inspections and desk-checking.
Used and Non-Functional testing.
The goal of verification is application and
 Goal The goal of validation is an actual product.
software architecture and specification.

Verification is typically performed by the

Validation is performed by the testing
 Responsibili quality assurance (QA) team, focusing on
team, which executes the software in real
reviewing documents, designs, and code to
environments to ensure it meets user
ty ensure compliance with specified
expectations and requirements.
requirements.

 Errors Verification is for prevention of errors. Validation is for detection of errors.

 Other Verification is also termed as white box Validation can be termed as black box
testing or static testing as work product goes testing or dynamic testing as work
Terminology through reviews. product is executed.
Case Study:
Therac-25
The Therac-25 was a radiation therapy machine used in hospitals, but its software
had serious flaws causing deadly accidents. Due to bugs in the user interface and
problems with concurrent programming (when two things happen at the same
time in code), the machine accidentally gave patients massive radiation overdoses.
These bugs weren’t caught because the software wasn't properly verified (checked
against design requirements)

Lesson:
Lack of thorough code verification and validation testing caused fatal accidents.
 TESTING TYPES :

. • WHITE BOX Testing

. • BLACK BOX Testing
. • GRAY BOX Testing
. • DEVELOPMENT Testing
. • PERFORMANCE Testing
. • REGRESION Testing
1) WHITE BOX TESTING :
 WHITE BOX Testing involves testing the internal structure and workings of a
software application.
The tester has access to the source code and uses this knowledge to design
test cases that can verify the correctness of the software .
This testing involves testing the product's architecture, and code to validate
input-output flow and enhance design, usability, and security.
White box testing analyzes the working of the software rather than just the
functionality as in black box testing.
It is also called glass box testing or open box testing or structural testing.
Unit testing,integration testing and stress testing are its types.
2) BLACK BOX TESTING :
BLACK BOX Testing not concerned with the internal knowledge or
implementation details of the software but rather focuses on
validating the functionality based on the provided specifications or
requirements.
Black box testing examines how system behaves from User's
perspective, without delving into the internal code or implementation
details.
Testers don't need to understand the system's internal structure or
programming language to perform black box testing.
Testers provide specific inputs to the system and observe the
corresponding outputs, verifying that the system behaves as
expected.
Test cases are derived from the system's specifications and focuses
on what the system is supposed to do rather than how it does it.
3)Gray Box Testing :

Gray Box Testing is a software testing technique that is a combination

of the Black Box Testing technique and the White Box
Testing technique. In the Black Box Testing technique, the tester is
unaware of the internal structure of the item being tested and in White
Box Testing the internal structure is known to the tester.
DEVELOPMENT TESTING
It is a method of applying testing practices continuously throughout the software
development life cycle process. This testing ensures the detection of bugs or errors at
the right time which further ensures delay of any kind of risk in terms of time and
cost. Development Testing aims to establish a framework to verify whether the
requirements of a given project are met in accordance with the rules of the mission to
be accomplished. This testing is performed by the software developers .They Detect
bugs like buffer overflows, unused variables, and logic errors
When to perform Development Testing?
• When building a new software product.
• When development cost is low, the client should perform development Testing so
that the client doesn’t have to face the debugging and another testing cost.
Tools for testing are TestingWhiz, HPE Unified Functional Testing,
Watir,Katalon Studio..

Example: In a calculator app, write a test for “divide by zero,”

implement the exception logic, and verify the app doesn’t crash.
Performance Testing:
It is a type of testing that ensures software applications perform
properly under their expected workload. It is a testing technique
carried out to determine system performance in terms of sensitivity,
reactivity, and stability under a particular workload.
The objective of performance testing is to make software stable and
reliable.And to evaluate the performance and scalability of a system or
application under various loads and conditions .
Regression Testing:
Regression Testing is a type of testing in SDLC that runs after every
change to ensure that the change introduces no unintended breaks.
Regression testing addresses a common issue that developers face —
the emergence of old bugs with the introduction of new changes.
ions.
Stress Testing:
Stress Testing is a software testing technique that determines the robustness
of software by testing beyond limits of normal operation. Stress testing is
more important for critical software but is used for all softwares. Stress
testing emphasizes robustness, availability, and error handling under a heavy
load . Stress testing is also known as Endurance Testing or Torture Testing .
• Stress testing includes changing variables including interest rates, market
conditions, transaction volumes and outside influences that could have an
impact on the system.
• Many departments in an organization work together and participate in
stress testing. This strategy makes sure that the stress testing procedure
benefits from a variety of viewpoints and specialties.
• Web tools for stress testing are LoadNinja,Jmeter,Webload,Smartmeter.