Monday, May 4, 2009

Integration Testing

Integration Testing

Integration testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested components and build a program structure that has been dictated by design.

Usually, the following methods of Integration testing are followed:

1. Top-down Integration approach.

2. Bottom-up Integration approach.

12.2.1 Top-Down Integration

Top-down integration testing is an incremental approach to construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main control module. Modules subordinate to the main control module are incorporated into the structure in either a depth-first or breadth-first manner.

 

  1. The Integration process is performed in a series of five steps:
  2. The main control module is used as a test driver and stubs are substituted for all components directly subordinate to the main control module.
  3. Depending on the integration approach selected subordinate stubs are replaced one at a time with actual components.
  4. Tests are conducted as each component is integrated.
  5. On completion of each set of tests, stub is replaced with the real component.
  6. Regression testing may be conducted to ensure that new errors have not been introduced.

12.2.2 Bottom-Up Integration

Bottom-up integration testing begins construction and testing with atomic modules (i.e. components at the lowest levels in the program structure). Because components are integrated from the bottom up, processing required for components subordinate to a given level is always available and the need for stubs is eliminated.

  1. A Bottom-up integration strategy may be implemented with the following steps:
  2. Low level components are combined into clusters that perform a specific software sub function.
  3. A driver is written to coordinate test case input and output.
  4. The cluster is tested.

Drivers are removed and clusters are combined moving upward in the program structure.

No comments:

Post a Comment