Page 48 - SOFTWARE TESTING & QUALITY ASSURANCE

Yadwinder Singh, Division of Examination Unit 4: White Box Testing

Unit 4: White Box Testing

CONTENTS
Objectives
Introduction
4.1 Static White Box Testing

4.1.1 Examining the Design and Code
4.1.2 Formal Review
4.1.3 Coding Standards and Guidelines
4.1.4 Code Review Checklist
4.2 Dynamic White Box Testing
4.2.1 Dynamic White Box Testing vs. Debugging
4.2.2 Testing the Pieces
4.2.3 Data Coverage

4.2.4 Code Coverage
4.3 Summary
4.4 Keywords
4.5 Self Assessment
4.6 Review Questions

4.7 Further Readings
Objectives

After studying this unit, you will be able to:
• Explain static white box testing

• Explain dynamic white box testing
Introduction
The IEEE definition of software lists four components which are needed in order to assure the quality of
software applications: computer programs or the code which is the brain behind any application;
procedures that define the flow of the program, its methods and the way of functioning; documentation
needed for developers and users; the data that includes parameters. The computer programs or the
source code of the software is an important artifact that needs to be tested for ensuring quality of the
software product. The testing that encompasses the verification of the computer programs and the logic
of the application is known as White Box testing.
IEEE defines White box testing as “The testing that takes into account the internal mechanism of a
system or component”. White box testing takes care of the intricacies of the product and evaluates it for
accuracy and precision, to meet the requirement specifications.
White box testing verifies the designs and codes involved in the development of a software product. It
involves validating whether the code has been implemented as per design specifications and also
validating the security concerns of the software’s functionality. Thus skilled testers with knowledge of
programming are required to conduct white box testing.

LOVELY PROFESSIONAL UNIVERSITY 41