UNIT IV

Black-Box Testing: What is Black-Box Testing - Why Black-Box

Testing– When to do Black Box Testing – How to do Black-Box Testing-
Compatibility testing
TEXT BOOK: “SOFTWARE TESTING Principles and Practices”-Srinivasan
Desikan & Gopalswamy Ramesh, 2006, Pearson Education
 Black-Box Testing
• What is Black-Box Testing
• Why Black-Box Testing
• When to do Black Box Testing
• How to do Black-Box Testing
 What is Black Box Testing?
• Black Box testing is done without the knowledge of the internals of
the system under test.
• Black Box testing involves looking at the specifications and does not
require examining the code of a program.
• Black Box testing is done from the customers view point.
 Why Black Box Testing
Black Box testing helps in the overall functionality verification of the
system under test.
• Black Box testing is done based on requirements.
• Black Box testing addresses the stated requirements as well as implied
requirements.
• Black box testing encompasses the end user perspectives.
• Black Box testing handles valid and invalid inputs.
 When to do Black Box Testing?
• Black box testing activities require involvement of the testing team
from the beginning of the software project life cycle, regardless of the
software development life cycle model chosen for the project.
• Testers can get involved right from the requirements gathering and
analysis phase for the system under test.
• Test scenarios and test data are prepared during the test construction
phase of the test life cycle, when the software is in the design phase.
 HOW TO DO BLACK BOX TESTING?
Black box testing exploits specifications to generate test cases in a methodical way to avoid
redundancy and to provide better coverage.
The Various techniques are
• Requirements based testing
• Positive and negative testing
• Boundary value analysis
• Decision tables
• Equivalence partitioning
• State based or Graph based testing
• Compatibility testing
• User documentation testing
• Domain testing
 Compatibility testing :
Compatibility testing is software testing which comes under the non functional
testing category, and it is performed on an application to check its compatibility
(running capability) on different platform/environments. This testing is done only when
the application becomes stable. Means simply this compatibility test aims to check the
developed software application functionality on various software, hardware platforms,
network and browser etc. This compatibility testing is very important in product
production and implementation point of view as it is performed to avoid future issues
regarding compatibility.
Types of Compatibility Testing :
Several examples of compatibility testing are given below.
1. Software :
 Testing the compatibility of an application with an Operating System like Linux, Mac,

Windows
 Testing compatibility on Database like Oracle SQL server, MongoDB server.

 Testing compatibility on different devices like in mobile phones, computers.

Types based on Version Testing :

There are two types of compatibility testing based on version testing
1. Forward compatibility testing : When the behavior and compatibility of a software
or hardware is checked with its newer version then it is called as forward
compatibility testing.
2. Backward compatibility testing : When the behavior and compatibility of a software
or hardware is checked with its older version then it is called as backward
compatibility testing.
2. Hardware :
Checking compatibility with a particular size of
 RAM

 ROM

 Hard Disk

 Memory Cards

 Processor

 Graphics Card

3. Smartphones :
Checking compatibility with different mobile platforms like android, iOS etc.
 4.Network :
Checking compatibility with different :
 Bandwidth

 Operating speed

 Capacity

Along with this there are other types of compatibility testing are also performed such as
browser compatibility to check software compatibility with different browsers like Google
Chrome, Internet Explorer etc. device compatibility, version of the software and others.
0 seconds of 15 secondsVolume 0%