ch3.ppt ppt of chapter 3 software testing
- 2. Levels of Testing Unit Testing Integration Testing Validation Testing Regression Testing Alpha Testing Beta Testing Acceptance Testing
- 4. Unit Testing Algorithms and logic Data structures (global and local) Interfaces Independent paths Boundary conditions Error handling
- 5. Why Integration Testing Is Necessary One module can have an adverse effect on another Subfunctions, when combined, may not produce the desired major function Individually acceptable imprecision in calculations may be magnified to unacceptable levels
- 6. Why Integration Testing Is Necessary (cont’d) Interfacing errors not detected in unit testing may appear Timing problems (in real-time systems) are not detectable by unit testing Resource contention problems are not detectable by unit testing
- 7. Top-Down Integration 1. The main control module is used as a driver, and stubs are substituted for all modules directly subordinate to the main module. 2. Depending on the integration approach selected (depth or breadth first), subordinate stubs are replaced by modules one at a time.
- 8. Top-Down Integration (cont’d) 3. Tests are run as each individual module is integrated. 4. On the successful completion of a set of tests, another stub is replaced with a real module 5. Regression testing is performed to ensure that errors have not developed as result of integrating new modules
- 9. Problems with Top-Down Integration Many times, calculations are performed in the modules at the bottom of the hierarchy Stubs typically do not pass data up to the higher modules Delaying testing until lower-level modules are ready usually results in integrating many modules at the same time rather than one at a time Developing stubs that can pass data up is almost as much work as developing the actual module
- 10. Bottom-Up Integration Integration begins with the lowest-level modules, which are combined into clusters, or builds, that perform a specific software subfunction Drivers (control programs developed as stubs) are written to coordinate test case input and output The cluster is tested Drivers are removed and clusters are combined moving upward in the program structure
- 11. Problems with Bottom-Up Integration The whole program does not exist until the last module is integrated Timing and resource contention problems are not found until late in the process
- 12. Validation Testing Determine if the software meets all of the requirements defined in the SRS Having written requirements is essential Regression testing is performed to determine if the software still meets all of its requirements in light of changes and modifications to the software Regression testing involves selectively repeating existing validation tests, not developing new tests
- 13. Alpha and Beta Testing It’s best to provide customers with an outline of the things that you would like them to focus on and specific test scenarios for them to execute. Provide with customers who are actively involved with a commitment to fix defects that they discover.
- 14. Acceptance Testing Similar to validation testing except that customers are present or directly involved. Usually the tests are developed by the customer
- 15. Test Methods White box or glass box testing Black box testing Top-down and bottom-up for performing incremental integration ALAC (Act-like-a-customer)
- 16. Test Types Functional tests Algorithmic tests Positive tests Negative tests Usability tests Boundary tests Startup/shutdown tests Platform tests Load/stress tests