Glass Box Testing Glass Box Testing o What
Glass Box Testing
Glass Box Testing o What is it? o How to do it.
Glass Box Testing o Typically done by development o Testing Levels n n n Unit Test Integration Test System Test
Unit Testing o Almost always Glass Box Testing o Usually needs stubs and drivers n Stubs – simple emulation of called routines p Return sample “realistic” or expected data p May return “bad” data to simulate errors n Drivers – calls program with test data p Good n Routine works ok p “Bad” n data Routine fails properly
Integration Testing o Several modules completed n Together provides a major function o These functions may be stand-alone o White or black box testing may be used n Development usually uses white box techniques n Test team usually does black box testing techniques
System Testing o Usually done with black box testing techniques o Usually done by Test team
Glass Box Testing o Use the source code n Find boundary conditions p Develop n tests to test boundaries Identify paths p Develop tests to ensure all paths are executed at least once n Identify subroutines/methods p Develop tests to exercise
Glass Box Testing o Debugging techniques n “printf” p “I am here” messages n Make sure every one is unique p Print intermediate values p Be sure to use unique identifiers n Debuggers p Set breakpoints p View and change variables
- Slides: 8