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
Q. Describe the Importance of function point? - This is independent of the languages tools or else methodology used for implementation. - They are able to be estimated from

Explain the Instruction pipelines Instruction pipelines: - An instructin pipeline reads consecutive instructions from memory whereas previous instructions are being implemented

What are the general activities in design process? i. System structuring - The system is separated into principle subsystems components and communications among these subsystem

Define KPAs level associated with maturity model KPAs are defined by SEI and associated with different maturity levels.  These are described below: Level 1 KPAs : There is

RAD Model Rapid Application Development Model is the method of incremental model. Achieves the high speed development using component based construction. Phases

Explain Software Bug? Ans) A fault in a program which origins the program to perform in an unintended or unanticipated manner.

program for full subtractor?

Q. Explain about token count - software metrics? Token count :- A program is considered to be series of tokens and if we count the number of tokens, some interesting results m

Define the Prototyping Model In this model, a working model of actual software is developed originally. Prototype is just like a sample software having low reliability and les

Describe how to perform Risk Analysis during software testing. While a test plan is being formed, risks involved in testing the product are to be taken into consideration with