BLACK BOX

TESTING
 Group Members
• Nirwan Sandesh-0059
• Dinusha Nimesh-0117
• Shaminda Rukshan-0102
• Hevindu Ravijayantha-0063
INTRODUCTION

• Black Box Testing is a software testing method where

the tester acts like a user. They focus on the software's
external behavior, providing inputs and observing
outputs, without needing knowledge of the internal
code. It's like testing a black box - you can interact with
it but can't see how it works inside. This approach helps
identify usability issues, ensure real-world functionality,
and deliver a smooth user experience.
WHAT IS BLACK BOX TESTING?

• Black-box testing is a method of software testing that

examines the functionality of an application without peering into
its internal structures or workings.
.
• This method of test can be applied virtually to every level of
software testing: unit, integration, system and acceptance.
• It is sometimes referred to as specification-based testing.
TYPES OF BLACK BOX TESTING

• Functional testing
Ensures software function as intended
Eg:- Unit, integration, system testing
• Non-functional testing
Evaluates system characteristics beyond functionality
Eg:- performance , usability , security testing
• Regression testing
Detects regression defects after changes in the software
 BENEFITS OF BLACK BOX TESTING

• Uncovers usability issues

Makes sure the software is easy and intuitive to use.
• Reveals real-world usage:
Tests how the software functions in scenarios users might encounter (like overloading the shopping cart).
• Enhances user experience:
Ensures the software meets user expectations for a smooth experience.
• Detects compatibility issues:
Tests how the software interacts with different browsers, operating systems, and devices.
 BLACK BOX TESTING TECHNIQUES

• Equivalence Partitioning
Divides input values into valid, invalid, and boundary partitions to test behavior within each (e.g., testing how
the shopping cart handles quantities of 1, 0, and negative numbers).
• Boundary Value Analysis
Focuses on testing inputs at the edges or boundaries of acceptable values (e.g., testing how the shopping cart
handles the maximum allowed number of items).
• User Interface Testing
Evaluates the usability, layout, and accessibility of the software interface (e.g., testing if the shopping cart
buttons are clear and easy to find).
PURPOSE OF BLACK BOX TESTING

• The purpose of Black Box Testing is to test software functionality from a user's
perspective. It ensures the software is usable, works in real-world situations, and delivers
a good user experience.
REAL WORLD EXAMPLES FOR BLACK BOX TESTING

• Website: Adding items to cart, checkout, verifying functionality and ease of use
(navigation, clear buttons).
• Mobile App: Ordering food, tracking delivery, ensuring functionalities work and the
interface is user-friendly. Testing on different phones to check compatibility.
• ATM: Withdrawing cash, checking balance, verifying core functions work and
instructions/screen displays are clear. Testing error handling (wrong PINs).
CHALLENGES IN BLACK BOX TESTING

• Limited code visibility

• Reproducing errors
• Dependency on test data quality
• Incomplete test courage
• Limited domain knowledge
• Time consuming test case design
Thank You…