Mindmap: What is Integration Testing

I was just explaining some students yesterday about Integration Testing. It was since so long I taught any batch. As there was lots of confusion among them about this, I created a small Mindmap for them. Sharing that mindmap here. If you want you can reuse it anywhere.

E-mail me when people leave their comments –

You need to be a member of Mobile QA Zone to add comments!

Join Mobile QA Zone


  • What is Integration Testing:
    1. The purpose of integration testing is to verify functional, performance, and reliability requirements placed on major design items. These "design items", i.e., assemblages (or groups of units), are exercised through their interfaces using black-box testing, success and error cases being simulated via appropriate parameter and data inputs

    2. Software integration testing is performed according to the software development life cycle (SDLC) after module and functional tests. The cross-dependencies for software integration testing are: schedule for integration testing, strategy and selection of the tools used for integration, define the cyclomatical complexity of the software and software architecture, reusability of modules and life-cycle and versioning management.

    3. Some different types of integration testing are big-bang, top-down, and bottom-up, mixed (sandwich) and risky-hardest. Other Integration Patterns[2] are: collaboration integration, backbone integration, layer integration, client-server integration, distributed services integration and high-frequency integration.

    Who performs Integration Testing:
    Either Dev teams themselves[on small scale] or independent QA teams(QA Service Providers) perform Integration Testing.

    APPROACHES and Type
    1. Big Bang : Big Bang is an approach to Integration Testing where all or most of the units are combined together and tested at one go. This approach is taken when the testing team receives the entire software in a bundle.

    2. Top Down: Top Down is an approach to Integration Testing where top level units are tested first and lower level units are tested step by step after that. This approach is taken when top down development approach is followed.
    3. Bottom Up : Bottom Up is an approach to Integration Testing where bottom level units are tested first and upper level units step by step after that. This approach is taken when bottom up development approach is followed.

    4.Sandwich/Hybrid: It is an approach to Integration Testing which is a combination of Top Down and Bottom Up approaches.


This reply was deleted.
Welcome to Mobile QA Zone, a Next Generation Software Testing Community.Invite your friends to join this community.Write to us to become a featured member.