CS447 Lecture Notes - Lecture 1: Unit Testing
Document Summary
First lowest layer of the hierarchy subsystem are tested, then the upper levels, until all system is tested together. Test top layer or controlling subsystem, then one level down, repeat until all are integrated. Sandwich combine top-down and bottom-up, middle layer is the target, need to converge to it. Unit testing of components then use sandwich strategy. Useful for integrating systems that don"t have much user interface ( oo, real time, strict performance ) Test cases are defined in terms of functionality ( user interface, can change it easily ) Top and bottom tests can be done in parallel. Test individual subsystems and their interfaces thoroughly before integration. Doesn"t work well for large programs; because its hard to know what caused the error. The user interface is tested last ( most important part ) , so can"t demo to people.
