Categories

A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

What is bottom-up integration testing?

– When the testing is carried out after combining the individual modules in to groups, it is called integration testing.
– This testing is carried out after the completion of the unit testing but before proceeding with the validation testing.
– The units that have been successful in the unit testing are taken as input in the integration testing and grouped together and then tested.
– The integration tests defined in the test plan are only applied to these unit aggregates.
– The integrated system after successful integration testing is ready to be subjected to system testing.
– The integration testing is used for the verification of the performance, functionality, reliability and requirements and so on.
– These are the requirements based up on the major design items.
– These design items are commonly known as the “assemblages”.
– Black box testing is used for exercising these assemblages through the interfaces.
– The simulation of the success and the error cases is done using the appropriate data inputs and the parameters.
– The simulation and the usage of the data areas of the shared is tested along with the inter – process communication.
– The exercising of the individual sub – systems is done via the input interface.
– The purpose behind the construction of the test cases is to test whether the individual components of the assemblages have proper interaction between them.
– The basic idea behind the integration testing is building block approach.
– The assemblages are verified and then added to the base that has already been verified.
– This hold set up is then used as a support for the integration testing of the other assemblages.

There are two types of integration testing namely:

  • The top – down integration testing and
  • The bottom – up integration testing
  • However there are some other integration patterns available:

  • Collaboration integration
  • Back bone integration
  • Layer integration
  • Client/ server integration
  • Distributed services integration
  • High – frequency integration
  • About Bottom – up Integration Testing

    – In this approach to the integration, the first components to be tested are lowest – level components.
    – These tested components are then used for facilitating the integration testing other higher level components.
    – This process continues until the top most component of the system is tested.
    – The low – level modules, functions and the procedures at the bottom are integrated prior to testing.
    – After the lower – level integrated modules have been subjected to integration testing, the modules for the next level are integrated and are used for integration testing.
    – Another point to be noted about the bottom – up testing is that it is useful only when almost all of the modules present at the same development level have successfully passed the integration testing.
    – Further, this approach also helps in the determination of the software levels that are already developed and also makes it easy for the reporting the progress of testing in percentage.
    – Here, the lower levels have to be tested extensively.
    – This is required because only then it can be guaranteed that the highest module that is used is subjected to proper testing.

    Following are some of the advantages of the bottom – up testing:

  • It makes the behavior between the interacting points quite clear. This is so because the addition of the components is controlled and has been subjected to repeated testing.
  • This is most appropriate kind of integration testing that have been developed using the bottom – up design methodology.
  • Following are the disadvantages of bottom – up type of integration testing:

  • In bottom – up integration testing it is quite difficult to write as well as maintain the test harnesses and the drivers. This is more difficult when compared to writing and maintaining test stubs.
  • Bottom – up integration testing cannot be used effectively for the applications that have been developed using the top – down design methodology.
  • The leftover modules that are also a part of the main program are taken one at a time and tested.

    Leave a Reply

    You can use these HTML tags

    <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>