Testing Levels (McConnel) Unit Testing Single programmer
involved in writing tested code Component Testing Multiple
programmers involved in writing test code Integration Testing
Testing two or more independently developed, interacting modules
together Regression Testing Use a set of tests that can be rerun
when changes are made to the system
Slide 3
Testing Transparency White-box Testing Tester has access to the
code Black-box Testing Tester has no access to the code Relies on
functional descriptions
Slide 4
Test Plan Test plan consists of a set of tests and the expected
results
Slide 5
Code coverage What parts of the code are actually executed by a
test? Statement coverage What combinations of sections of code are
executed by a test? Conditional Coverage (all conditions are
evaluated as true at least once and as false at least once)
Slide 6
Boundary Values Identify equivalence classes Array declaration
example: Good test cases usually test the boundary values of inputs
Empty strings Max number of array elements
Slide 7
Finding Equivalence Classes: C++ Array Declaration Input
ConditionValid Equivalence classesInvalid Equivalence classes Size
of array name255 truncates to 255 (3)
