Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumTypes Of Software Testing @ OneStopTestingIntegration Testing @ OneStopTesting

Message Icon Topic: Integration Testing

Post Reply Post New Topic
Author Message
tanushree
Senior Member
Senior Member
Avatar

Joined: 04Apr2007
Online Status: Offline
Posts: 2160
Quote tanushree Replybullet Topic: Integration Testing
    Posted: 22Oct2007 at 3:48am
Integration Testing:-

              Testing in which software components, hardware components, or both together are combined and tested to evaluate interactions between them.
Integration testing takes as its input modules that have been checked out by unit testing, groups them in larger aggregates, applies tests defined in an Integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.
                           
What:
Testing performed to expose faults in the interfaces and in the interaction between integrated components.

Who will do:
As integration testing covers broad length of ‘V’ model. From the developers to System integrators will involve.

Where it:
Almost all integration will takes place at the developing organization sites.


Integration testing can be conducted in two ways.
1) Non-Incremental Approach
2) Incremental Approach

1) Non-Incremental Approach:
The non incremental approach is also known as “Big-Bang” testing. This approach is very unfashionable due to the level of risk that one takes in hoping that the system will perform as expected.

2) Incremental Approach:
Incrementally integration testing can be split in to
a) Top-down Testing
b) Bottom-up Testing
c) Sandwich (Hybrid) Testing
                             
a) Top-down Testing:
In Top-down Testing, higher level modules are tested. If lower modules required to make up the system are not yet available then, stubs are used to simulate their activity.

Stub: Small software placed in to a program that provides a common function.

b) Bottom-up Testing:
In Bottom-up testing, lower level modules are tested. If the higher level modules required to make up the system are not yet available then, drivers are used to simulate their activity.

Driver: Drivers are simple program designed specifically for testing that make calls to these lower layers.

c) Sandwich Testing:
Sandwich testing is a hybrid between Bottom-up and Top-down testing. It will test the user interface in isolation using Stubs and test the very lowest functions using drivers.



Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
getzephyr
Groupie
Groupie


Joined: 25Jan2008
Online Status: Offline
Posts: 47
Quote getzephyr Replybullet Posted: 21Jun2008 at 3:03am
Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested.

Objective of Integration testing is to make sure that the interaction of two or more components produces results that satisfy functional requirement. In integration testing, test cases are developed with the express purpose of exercising the interface between the components.

IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.695 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting