高级软件工程课件-软件测试.ppt

8.4 Integration TestingTop-Down Integration Example Only A is tested by itself 8.4 Integration Testing Modified Top-Down Integration Example Each level’s components individually tested before the merger takes place 8.4 Integration Testing Bing-Bang Integration Example Requires both stubs and drivers to test the independent components 8.4 Integration Testing Sandwich Integration Example Viewed system as three layers 8.4 Integration Testing Modified Sandwich Integration Example Allows upper-level components to be tested before merging them with others 8.4 Integration TestingComparison of Integration Strategies Bottom-up Top-down Modified top-down Bing-bang Sandwich Modified sandwich Integration Early Early Early Late Early Early Time to basic working program Late Early Early Late Early Early Component drivers needed Yes No Yes Yes Yes Yes Stubs needed No Yes Yes Yes Yes Yes Work parallelism at beginning Medium Low Medium High Medium High Ability to test particular paths Easy Hard Easy Easy Medium Easy Ability to plan and control sequence Easy Hard Hard Easy Hard hard 8.4 Integration TestingSidebar 8.5 Builds at Microsoft The feature teams synchronize their work by building the product and finding and fixing faults on a daily basis 8.6 Test Planning Establish test objectives Design test cases Write test cases Test test cases Execute tests Evaluate test results 8.6 Test PlanningPurpose of the Plan Test plan explains who does the testing why the tests are performed how tests are conducted when the tests are scheduled 8.6 Test PlanningContents of the Plan What the test objectives are How the test will be run What criteria will be used to determine when the testing is complete 8.7 Automated Testing Tools Code analysis Static analysis code analyzer structure checker data analyzer sequence checker Output from static analysis 8.7 Automated Testing Tools (continued) Dynamic analysis program monitors: watch and report program’s behavior Test execution Capture a