S O F TWA R E
E N G I . . . . .
WHITE BOX TESTING
P R E S E N TAT I O N
TITLE: INTRODUCTION TO WHITE BOX TESTING
S U B T I T L E : W H AT I T I S , H O W I T W O R K S , A N D W H Y I T ’ S
I M P O R TA N T
02
WHAT IS WHITE BOX TESTING?
Definition :
White Box Testing is a method where the tester
looks inside the software and tests how it works.
They can see the code and test how it runs.
What do testers focus on?
⚬ The code itself.
⚬ The logic of the program (how it makes decisions).
⚬ The paths the program can take when running.
03
TYPES AND TECHNIQUES OF WHITE BOX TESTING
Unit Testing :
Tests small parts of the software (like a single function) to make sure
they work corectly .
Integration Testing:
Tests how different parts of the software work together.
Techniques Used:
• Control Flow Testing: Makes sure all decisions (like "if" or "else") are
checked.
• Data Flow Testing: Looks at how data moves through the program.
• Path Testing: Checks all possible ways the program can run.
04
ADVANTAGES AND DISADVANTAGES
• Needs Programming Skills: Testers must
• Thorough Testing: Tests the code deeply.
know how to code.
• Find Bugs Early: Bugs are found early in
• Takes Time: Testing all parts of the code can
development.
take time.
• Better Code Quality: Helps improve the
• Doesn't Test User Experience: Doesn’t look at
software’s performance
how users interact with the program.
05
CONCLUSION :
• White Box Testing looks inside the software to check how it works.
• Why it’s good: It helps find bugs and improves the software’s code.
• Challenges: It takes time and requires testers to know how to code.
• Best Practice: Combining White Box Testing with other tests (like Black Box
Testing) gives the best results.
06
THANK YOU
S O F TWA R E
E N G . . . . . . .
