|
OO Integration Testing
Glossary of Software QA/Testing
(Continued from previous question...)
OO Integration Testing
This strategy involves testing the classes as they are integrated into the system. The traditional approach would test each operation separately as they are implemented into a class. In OO system this approach is not viable because of the "direct and indirect interactions of the components that make up the class"
.
Integration testing in OO can be performed in two basic ways :
- Thread-based - Takes all the classes needed to react to a given input. Each class is unit tested and then thread constructed from these classes tested as a set.
- Uses-based - Tests classes in groups. Once the group is tested, the next group that uses the first group (dependent classes) is tested. Then the group that uses the second group and so on. Use of stubs or drivers may be necessary.
Cluster testing is similar to testing builds in the traditional model. Basically collaborating classes are tested in clusters.
(Continued on next question...)
Other Interview Questions
| 