Page 270 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Principles of Software Engineering

Notes 13.4.2 Types of Black Box Testing
Functional Testing

This black box testing type is related to functional requirements of a system; it is done by
software testers.

Non Functional Testing
This type of black box testing is not related to testing of a specific functionality, but non functional
requirements such as performance, scalability, usability.

Black Box Testing Strategy
Following are the prominent test strategy amongst the many used in Black box Testing.

Equivalence Class Testing
It is used to minimize the number of possible test cases to an optimum level while maintains
reasonable test coverage.

Boundary Value Testing
Boundary value testing is focused on the values at boundaries. This technique determines whether
a certain range of values are acceptable by the system or not. It is very useful in reducing the
number of test cases. It is mostly suitable for the systems where input is within certain ranges.

Decision Table Testing
A decision table puts causes and their effects in a matrix. There is unique combination in each
column.

13.4.3 Black Box Testing and Software Development Life Cycle (SDLC)
Black box testing has its own life cycle called Software Test Life Cycle. it is relative to every
stage of Software Development Life Cycle.
Requirement

This is the initial stage of and in this stage requirement is gathered. Software testers also take
part in this stage.
Test Planning and Analysis

Test plan is created which determines possible project risks and their mitigation.
Design

In this stage Test cases/scripts are created on the basis of software requirement documents.
Test Execution
In this stage Test Cases prepared are executed. Bugs if any are fixed and re tested.

Draw the structure of white box testing.

13.4.4 Advantages and Disadvantages of Black Box Testing

In black box testing, the internals of the system are not taken into consideration. The testers do
not have access to the source code. A tester who is doing black box testing generally interacts
through a user interface with the system by giving the inputs and examining the outputs. The

264 LOVELY PROFESSIONAL UNIVERSITY