Similar Posts

2 Comments

  1. Hello Raj.
    First of all I am thankful to you that you made such a easy and simple website for us to learn Testing.

    I have one simple question ?

    i.e. “What are actually these STUBS and DRIVERS in Integration Testing ?”

    Hoping for your kind response.

    1. Hi Tanuj Singh, These terms come into the picture while doing Integration Testing. While working on integration, sometimes we face a situation where some of the functionalities are still under development. So the functionalities which are under development will be replaced with some dummy programs. These dummy programs are named as Stubs or Drivers.

      Imagine, we have two pages i.e., Login page and Admin page.

      You have to test Login page (assume, Admin page is under development). The login page will call the Admin page after login but the Admin page is not ready yet. To overcome this situation developers write a dummy program which acts as Admin page. This dummy program is AKA Stub.
      Stubs are ‘Called programs’. If a ‘Called program’ is incomplete, it is replaced with Stub. (This happens in Top down approach)

      Coming to Drivers. In the above example, the Login page is ready but not the Admin page. this time assume that the Admin page is ready to test but the Login page is not ready yet. To overcome this situation developers write a dummy program which acts like Login page. This dummy program is AKA Driver. Drivers are ‘Calling programs’. If a ‘Calling program’ is incomplete, it is replaced with Driver. (This happens in bottom up approach)

      Hope you are clear now.

Leave a Reply

Your email address will not be published. Required fields are marked *