第五章 集测试.pptVIP

CS140 - Winter 2007 - Handout #1 第5章 集成测试 5.1 深入研究SATM系统 5.2 集成测试的主要方法 5.2.1 基于功能分解的集成 5.2.2 基于调用图的集成 5.2.3 基于路径的集成 5.3 案例研究 SATM系统的功能分解 5.2.1基于功能性分解的集成 两种表示方式 树和文字形式 集成的4种模块顺序 从树顶开始向下：自顶向下(Top-down) 从树底开始向上：自底向上(Bottom-up) 三明治方法: Sandwich 大爆炸方法：Big Bang 大爆炸集成测试 自顶向下集成 自顶向下集成（续） Advantages and Disadvantages of Top-Down Integration Testing Test cases can be defined in terms of the functionality of the system (functional requirements). Structural techniques can also be used for the units in the top levels Writing stubs can be difficult especially when parameter passing is complex. Stubs must allow all possible conditions to be tested Possibly a very large number of stubs may be required, especially if the lowest level of the system contains many functional units One solution to avoid too many stubs: Modified top-down testing strategy (Bruege) Test each layer of the system decomposition individually before merging the layers Disadvantage of modified top-down testing: Both, stubs and drivers are needed 自底向上集成 自底向上集成（续） Advantages and Disadvantages of Bottom-Up Integration Testing Not optimal strategy for functionally decomposed systems: Tests the most important subsystem (UI) last Useful for integrating the following systems Object-oriented systems Real-time systems Systems with strict performance requirements 三明治集成 Advantages and Disadvantages of Sandwich Integration Testing Top and Bottom Layer Tests can be done in parallel Does not test the individual subsystems thoroughly before integration Solution: Modified sandwich testing strategy (Bruege) Steps in Integration-Testing 1. Based on the integration strategy, select a component to be tested. Unit test all the classes in the component. 2. Put selected component together; do any preliminary fix-up necessary to make the integration test operational (drivers, stubs) 3. Do functional testing: Define test cases that exercise all uses cases with the selected component 4. Do structural testing: Define test cases t