Integration Testing

Integration Testing Introduction:

Integration testing is the phase in software testing in which individual software modules are combined & tested as a group. It occurs after unit testing & before validation testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests that defined in an integration test plan to those aggregates & delivers as its output the integrated system ready for system testing.

Overview Of Integration Testing Job Support:

Integration testing is also known as integration & testing, is a software development process which program units are combined & 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, a pragmatic method of software development that takes a meticulous approach to building a product by means of a continual testing & revision.

There are two major ways of carrying out an integration test called the bottom-up method & the top-down method. Bottom-up integration testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules / builds. In top-down integration testing, the highest-level modules are tested first  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 that concludes with multiple tests of the complete application, preferably in scenarios designed to mimic those it will encounter in customers computers, systems & networks.

Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component & the interface between them is tested. The idea is to test combinations of pieces & eventually expand the process to test your modules with those of other groups. Eventually all the modules making up a process are tested together. Beyond that, if the program is composed of more than one process, they should be tested in pairs rather than all at once.

Integration testing identifies problems that occur when units are combined. By using a test plan that requires you to test each unit & ensure the viability of each before combining units, you know that any errors discovered when combining units are likely related to the interface between units. This method reduces the number of possibilities to a far simpler level of analysis.

Working Hours

  • Monday9am - 6pm
  • Tuesday9am - 6pm
  • Wednesday9am - 6pm
  • Thursday9am - 6pm
  • Friday9am - 6pm
  • SaturdayClosed
  • SundayClosed

Charlie Brown
Web Designer
My name is Ruth. I grew up and studied in…
Jackson James
Web Designer
Praesent varius orci at erat lobortis lacinia. Morbi lectus metus,…
View All
Latest Posts

View All
Show Buttons
Hide Buttons