integration testing
Home > Software Quality Glossary > Definition - integration testing
EMAIL THIS
Glossary - powered by WhatIs.com
 BROWSE ALPHABETICALLY:    A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #    

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 it:
>>  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.

Last updated on: Jul 02, 2008

WHITE PAPERS  
Optimizing the Application Testing of Your Siebel CRM Environment
Hewlett-Packard Company

Move Web Application Security Testing into Your Development Cycle
IBM

Strategic Quality Assurance: How Much Testing Is Enough?
Telelogic, An IBM Company

Introduction to the Real Time Performance Monitor (RTPM)
Azul Systems, Inc

Five Best Practices for Improving Software Development and Testing
VMLogix

>> More White Papers



  WHAT'S NEW
 1. Optimizing Performance in the Enterprise
 2. Requirements gathering techniques
 3. Handbook of Agile Software Craftsmanship
 4. Software testing fundamentals
 


About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2006 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts