1 / 14

Integration Testing

Integration Testing. 12/09. Integration Testing. Assumes the units have been tested individually Tests units working together Identifies errors in the interfaces between units. Big-bang integration. Test all components in isolation, then mix them all together and see how it works

tallulah
Download Presentation

Integration Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integration Testing 12/09

  2. Integration Testing • Assumes the units have been tested individually • Tests units working together • Identifies errors in the interfaces between units

  3. Big-bang integration • Test all components in isolation, then mix them all together and see how it works • As all components are merged at once, it is difficult to identify the cause of a failure

  4. Test Procedures

  5. Top-Down Integration Testing • Modules are integrated by moving downward through control hierarchy • Modules subordinate to main control module are incorporated • Depth-first • Breadth-first M1 M2 M3 M4 M5 M6 M7 M8

  6. Steps in Top-Down Integration Testing • The main module is used as a test driver • Stubs are substituted for all components directly subordinate to the main control module

  7. Top-Down Integration Strategy • Verifies major control or decision early in the test process. • Allows early recognition of problems • Depth first strategy allows a complete function of the software to be implemented

  8. Bottom-Up Integration • Low-level components are combined into clusters • A driver is written to coordinate test case input and output • Cluster is tested • Drivers are removed and clusters are combined moving upward in program structure.

  9. Bottom Up Integration Testing In Bottom Up: M1 M2 M3 M4 M5 M6 M7 M8

  10. Bottom-Up Integration • Begins construction and testing with atomic modules • Need for stubs is eliminated • Operational modules tested thoroughly

  11. Sandwich integration-1 • Combination of bottom-up and top-down integrations • System is viewed as layers • Top-down approach is used for the top layer • A bottom-up approach is used for the bottom layer

  12. Sandwich integration-2 • Combination of bottom-up and top-down integrations • System is viewed as layers • Start with a layer in the middle • Use drivers to and stubs to check

  13. Regression Testing-1 • Adding new or changing module impacts the system • New data flow paths established • New I/O may occur • New control logic invoked • Regression testing is re-execution of subset of tests that have already been conducted • Ensures changes have not propagated unintended side effects

  14. Regression Test-2 • Approaches • Test suite contains following classes of test cases:

More Related