CHAPTER 3: BLACK BOX TESTING

Functional (Black Box) Testing

Disadvantages of Black Box Testing
 Behavioral and operational testing
 A tester can test only a small number of
 Testing the internal logic without knowing how
possible inputs
exactly the software Works.
 It is very difficult to design test cases if
 Depends on the output
specifications are not clear or concise.
 Developing the test case is very essential
 Bugs can go undetected.
 Testing search engine is a good example
Black box testing attempts to find the
Advantages of Black Box testing following.
 Testers do not have to understand the internal  Errors in interface
working of the software.
 Data structure Errors
 Deals with GUI for output.
 Performance errors
 Helps to expose any ambiguities or
 Initialization and terminal errors
inconsistencies in the specifications
CONT’D…
Advantages of White Box Testing
White Box testing
 It is very easy to build test cases
 Glass box testing
 Helps to optimize the code
 Focus on the structure of the code
 Extra lines of code can be removed
 Verification process
Disadvantage of White Box Testing
 Check efficiency of the code
 Highly impossible to check every code
written
 Skilled testers are required
 She/he needs to know the
 The time to carry out this test for complex
programming concept
software is very high.

 STATIC BLACK BOX TESTING AND DYNAMIC BLACK BOX TESTING TECHNIQUES

Static Black Box Testing Techniques • Some examples of the various

 Testing software without compilation
 Perform the test to check the specifications
sources from where standards
(documents)
and guidelines can be adapted.
 The mobile user manual is an example of
specification document  Conventions Followed by Corporates

 more research oriented  Industry Requirements:

Static black box testing - High Level Specification  Government Standards

Test Technique  Graphical User Interface (GUI)
 it requires a methodical approach to view the
 Security Standards
specification
 STATIC BLACK BOX TESTING - LOW LEVEL SPECIFICATION TEST
TECHNIQUE
Since Low-level specification looks out for clarity
of the explanation, a tester has to keenly test
High level specification testing focuses on whenever he/she encounters the following
words:
external influences, whereas low level  Always, None, All, Never
specification test focuses on the  A tester has to foresee where the conditions could
be violated
following eight attributes:  Certainly, Clearly, Obviously, Evidently
 These words are persuasive words which
 Completeness should be tested
 Etc., And So on
 Accuracy  It is best such words are avoided
 Some, Sometimes, Often, Usually, Mostly
 Precision, Unambiguity and Clarity  Vague words like these need to be avoided.
 Good, Fast, Cheap, Efficient, Small:
 Relevance
 Unquantifiable terms such as these need to be
 Feasibility avoided

 Code-free Explanation
 Testable
DYNAMIC BLACK BOX TESTING
• Testing is carried out with data Data Testing
• Tester is able to observe the change  Based on the concept of
exhibited by the system. equivalence partitioning, the
• A software Application undergoes a testing can be carried out on the
dynamic black box test. following four levels
• Various techniques used to perform  Boundary conditions
dynamic black box testing
 Sub-boundary conditions
 Test to Pass and Test to Fail
 Nulls
 Push the software to the extreme
 Bad data
 Equivalence Partitioning

 Identify the test case


State Testing
 Used for high level black box testing like
for object oriented programming language
Random Testing
 The tester provides random inputs to the test
software and checks the output of the
software against the expected output.
 Popular testing also known as Gorilla
testing or Ad hoc testing
Mutation Testing
 The tester makes minor
modifications in the program’s
source code and performs the test
 The main objective of this testing
is to check the behavior of the
code when some modification is
made to the original one.