integration testing

Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.

There are two major ways of carrying out an integration test, called the bottom-up method and the top-down method. Bottom-up integration testing begins with unit testing, followed by tests of of progressively higher-level combinations of units called modules or builds. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that. In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing. The process concludes with multiple tests of the complete application, preferably in scenarios designed to mimic those it will encounter in customers' computers, systems and networks.

Getting started with use integration testing

To explore how integration testing is used in the enterprise, here are some additional resources for learning about testing:

How to do integration testing: The top-down and bottom-up approaches for integration testing are both critical. Expert John Overbaugh explains the differences between them and the reasons for their importance.

Functional testing: Unit testing, integration testing and beyond: Integration tests and unit tests both test the functionality of software, but they alone cannot replace functional testing. Expert Karen N. Johnson explains how integration and unit tests work and offers ideas for other functional tests.

Read more about integration testing: - The Open Process Framework Repository Organization (OPFRO) outlines the integration testing process. - Jeffrey Palermo provides a simple demonstration of integration testing. - Mark Seemann discusses some principles of integration testing. - Emerson Process Management offers an integration testing service.

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT What is system integration testing? What exactly is system integration testing? At what stage is it done? Do you need to prepare a separate integration test plan? What type of designs are needed to write integration test cases? A user asks, "What type of design documents/designs (data flow, use case) exactly are required to write integration test cases?" Mike Kelly provides... Who is responsible for integration testing, developer or tester? Responsibility for integration testing depends on the project and the company -- but ideally, the two roles will collaborate in this area.

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary continuous integration  (SearchSoftwareQuality.com) Continuous integration (CI) is a software engineering practice in which developers integrate their work frequently. The practice is thought to enable... V-Model  (SearchSoftwareQuality.com) The V-Model, also called the Vee-Model, is a product-development process originally developed in Germany for government defense projects......