软件测试策略讲义.ppt

17.5webapp的测试策略 17.6确认测试 17.8调试技巧 17.8.1 17.8.3调试策略 * Top Down Integration top module is tested with stubs stubs are replaced one at a time, depth first as new modules are integrated, some subset of tests is re-run A B C D E F G * Bottom-Up Integration drivers are replaced one at a time, depth first worker modules are grouped into builds and integrated A B C D E F G cluster * Regression Testing Regression testing is the re-execution of some subset of tests that have already been conducted to ensure that changes have not propagated unintended side effects Whenever software is corrected, some aspect of the software configuration (the program, its documentation, or the data that support it) is changed. Regression testing helps to ensure that changes (due to testing or for other reasons) do not introduce unintended behavior or additional errors. Regression testing may be conducted manually, by re-executing a subset of all test cases or using automated capture/playback tools. * Smoke Testing A common approach for creating “daily builds” for product software Smoke testing steps: Software components that have been translated into code are integrated into a “build.” A build includes all data files, libraries, reusable modules, and engineered components that are required to implement one or more product functions. A series of tests is designed to expose errors that will keep the build from properly performing its function. The intent should be to uncover “show stopper” errors that have the highest likelihood of throwing the software project behind schedule. The build is integrated with other builds and the entire product (in its current form) is smoke tested daily. The integration approach may be top down or bottom up. * 17.4Object-Oriented Testing begins by evaluating the correctness and consistency of the analysis and design models testing strategy changes the concept of the ‘unit’ broadens due to encapsulation integration focuses on classes and their execution