Briefly explain integration testing, Software Engineering

Q. Briefly explain Integration Testing?

Integration Testing: In this the module are methodically integrated and tested to find protocol design error, interface problems, errors due to global values, input/ output format errors etc. Diverse strategies can be:

  • Bottom up Integration: In this kind of testing the modules at the leaf level are first tested and then we move up in the hierarchy. Drivers are utilized in this type of testing at different levels of hierarchy. Driver is a program which accept the test case data to be inputted and printed by the module to be tested.
  • Top Down Integration: In this case we start the top mainly module in the hierarchy and move down till the leaf modules are tested. Where ever necessary necessary stubs/ drivers are used. A stub is a program which simulate the module called by the module to be tested.
  • Big-Bang Testing: In this all the modules subsequent to unit testing are combined and tested in one go. The problem with this forms of testing is debugging of errors.
  • Sandwich Testing: This technique makes utilization of combination of top down and Bottom up testing.

 

Posted Date: 7/26/2013 3:28:17 AM | Location : United States







Related Discussions:- Briefly explain integration testing, Assignment Help, Ask Question on Briefly explain integration testing, Get Answer, Expert's Help, Briefly explain integration testing Discussions

Write discussion on Briefly explain integration testing
Your posts are moderated
Related Questions
Explain fully the application of artificial intelligence

Smoke testing It decreases the integration risk. Error diagnosis and correction are simplified

You want to record a data driven test. How will you do that? There are 3 ways to create a data-driven test: a.) By using data from a data table b.) By using data from a f

Checks the interfaces among program elements for consistency and adherence to predefined axioms or rules.

Determine the System Integration the life cycle process. It is the process of putting hardware, software and user together to prepare a system. System Installation I

Explain any ten case tools

State the System Engineering Hierarchy? The world view is composed of a set of domains (Di), which can each be a system, or system of systems. WV = {D1,D2,D3,...........,Dn}

Why software change occurs? Software change happens because of the following reasons. New needs emerge when the software is used. The business environment changes. Errors need

Consider a program for the purpose of the nature of roots of a quadratic equation. Its input is the triple of positive integers say a, b, c as well as values in the interval [0,100

The important issues that a SRS must address are:  (a) System goals and requirements are different (b) Request Definition (c) Request Specification (d) Software Specif