Articles

What is Integration Testing? Software Testing Tutorial

May 17, 2019



integration testing in this phase of testing individual modules are combined and tested as a group data transferred between the modules is tested thoroughly integration testing is carried out by testers consider this integration testing scenario in a banking application a customer is using the current balance module his balance is 1,000 he navigates to the transfer module and transfers 500 to a third-party account the customer navigates back to the current balance module and now his latest balance should be 500 the modules in this project are assigned to five different developers to reduce coding time kotor 2 is ready with the current balance module kotor 5 is not ready with the transfer module required to test your integration scenario what do you do in such a situation one approach is to use BIGBANG integration testing where you wait for all modules to be developed before you begin testing the major disadvantage is that it increases project execution time since testers will be sitting idle until all modules are developed also it becomes difficult to trace the root cause of defects alternatively you could use the incremental approach where modules are checked for integration as and when they are available consider that the transfer module is yet to be developed but the current balance module is ready you will create a stub which will accept and give back data to the current balance module note that this is not a complete implementation of the transfer module which will have lots of checks like whether the third-party account number is entered correct the amount to transfer should not be more than the amount available in the account and so on but it will just simulate the data transfer that takes place between the two modules to facilitate testing on the contrary if the transfer module is ready but the current balance module is not developed you will create a driver to simulate transfer between the modules to increase the effectiveness of the integration testing you may use a top to down approach where higher-level modules are tested first this technique will require creation of stubs or you may use a bottom-up approach where lower-level modules are tested first this technique will require creation of drivers other approaches would be functional increment and sandwich which is a combination of top to down and bottom to up the choice of approach chosen depends on the system architecture and the location of high-risk modules

You Might Also Like

22 Comments

  • Reply Guru99 May 17, 2019 at 9:41 am

    Check out our FREE Real Time Testing Project: https://www.guru99.com/live-testing-project.html

  • Reply Kieran 't Hart May 17, 2019 at 9:41 am

    Great explanation 🙂

  • Reply L Ishi May 17, 2019 at 9:41 am

    Is integration testing a black box testing or white box testing? Is it done by developers or testers? please help me out.

  • Reply Anuj Sharma May 17, 2019 at 9:41 am

    Honestly i wish you were my professor! Very well explained and it such short time!
    Thank you!

  • Reply Тимур Бибарсов May 17, 2019 at 9:41 am

    Good video, but I also expected to see how Driver and Stub classes must be written, too short explanation

  • Reply Himanshu Singh May 17, 2019 at 9:41 am

    great animations

  • Reply mr nothing May 17, 2019 at 9:41 am

    The clipart/Pictures and animations in the presentations are well coordinated.

    very good job!

  • Reply mr nothing May 17, 2019 at 9:41 am

    Excellent videos.. Thanks!

  • Reply mr nothing May 17, 2019 at 9:41 am

    You can not get better understanding of Testing anywhere else..

    best videos ever.

    well planned, organized, sequenced, and executed information..

    the guy who is asked to do the dubbing job on the video speaks very clear as well.. knows how to articulate while uttering..

    amazing…

    excellent job done guys!

  • Reply Asif Redmi May 17, 2019 at 9:41 am

    super..
    Thanks a lot

  • Reply Dibyanka mahto May 17, 2019 at 9:41 am

    very helpful!

  • Reply its me May 17, 2019 at 9:41 am

    for integration testing..who is gonna integrate those unit tested individual modules ? We will only do the testing of how modules react right ?

  • Reply puneeth shivalingaiah May 17, 2019 at 9:41 am

    Excellent 🙂 🙂 🙂

  • Reply obamer May 17, 2019 at 9:41 am

    Very helpful thank you

  • Reply Артем Арте May 17, 2019 at 9:41 am

    This is not a integration testing, this is functional (end-to-end) testing. Integration testings tests just the border between two systems, but not the scenrio. For example integration testing tests CRUD for database tables and verifies that the data at lease will send or received, or mapping is correct, but who cares what user story do you implement? To test user stories you have to have all set of your systems and subsystems you will use.

    So, testsers write articles for testers without knowledge what is integration testing.

  • Reply Freelance Software Test May 17, 2019 at 9:41 am

    Very imformative. Thanks Guru99

  • Reply Kruthiga K May 17, 2019 at 9:41 am

    Excellent work!! Thank you so much 🙂

  • Reply Orville Nim Rosillo May 17, 2019 at 9:41 am

    Superb! explanation. thanks

  • Reply Diksha May 17, 2019 at 9:41 am

    Thank you very much!

  • Reply Nassim B. May 17, 2019 at 9:41 am

    or you can finish your project in 1 day by using only drivers and stubs

  • Reply Mr. A May 17, 2019 at 9:41 am

    +Guru99  sir/mam can u please tell me which software or tools you used for creating this video . thanks 
    anuj

  • Reply Ivan Čabarkapa May 17, 2019 at 9:41 am

    Great explanation! Tnx

  • Leave a Reply