Topic: Integration Test Plan

Message

   Integration Test Plan
The
integration test plan is the overall plan for carrying out the
activities in the integration test level, which contains the following
sections.

What is to be tested?
This
section clearly specifies the kinds of interfaces fall under the scope
of testing internal, external interfaces, with request and response is
to be explained. This need not go deep in terms of technical details
but the general approach how the interfaces are triggered is explained.

Sequence of Integration
When
there are multiple modules present in an application, the sequence in
which they are to be integrated will be specified in this section. In
this, the dependencies between the modules play a vital role. If a unit
B has to be executed, it may need the data that is fed by unit A and
unit X. In this case, the units A and X have to be integrated and then
using that data, the unit B has to be tested. This has to be stated to
the whole set of units in the program. Given this correctly, the
testing activities will lead to the product, slowly building the
product, unit by unit and then integrating them.

List of Modules and Interface Functions
There
may be N number of units in the application, but the units that are
going to communicate with each other, alone are tested in this phase.
If the units are designed in such a way that they are mutually
independent, then the interfaces do not come into picture. This is
almost impossible in any system, as the units have to communicate to
other units, in order to get different types of functionalities
executed. In this section, we need to list the units and for what
purpose it talks to the others need to be mentioned. This will not go
into technical aspects, but at a higher level, this has to be explained
in plain English.

Apart from the above sections, the following sections are addressed, very specific to integration testing.
•   Integration Testing Tools
•   Priority of Program interfaces
•   Naming convention for test cases
•   Status reporting mechanism
•   Regression test approach
•   ETVX criteria
•   Build/Refresh
criteria {When multiple programs or objects are to be linked to arrived
at single product, and one unit has some modifications, then it may
need to rebuild the entire product and then load it into the
integration test environment. When and how often, the product is
rebuilt and refreshed is to be mentioned}.

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: Integration Test Plan Posted: 15Oct2007 at 4:09am
	Integration Test Plan The integration test plan is the overall plan for carrying out the activities in the integration test level, which contains the following sections. What is to be tested? This section clearly specifies the kinds of interfaces fall under the scope of testing internal, external interfaces, with request and response is to be explained. This need not go deep in terms of technical details but the general approach how the interfaces are triggered is explained. Sequence of Integration When there are multiple modules present in an application, the sequence in which they are to be integrated will be specified in this section. In this, the dependencies between the modules play a vital role. If a unit B has to be executed, it may need the data that is fed by unit A and unit X. In this case, the units A and X have to be integrated and then using that data, the unit B has to be tested. This has to be stated to the whole set of units in the program. Given this correctly, the testing activities will lead to the product, slowly building the product, unit by unit and then integrating them. List of Modules and Interface Functions There may be N number of units in the application, but the units that are going to communicate with each other, alone are tested in this phase. If the units are designed in such a way that they are mutually independent, then the interfaces do not come into picture. This is almost impossible in any system, as the units have to communicate to other units, in order to get different types of functionalities executed. In this section, we need to list the units and for what purpose it talks to the others need to be mentioned. This will not go into technical aspects, but at a higher level, this has to be explained in plain English. Apart from the above sections, the following sections are addressed, very specific to integration testing. • Integration Testing Tools • Priority of Program interfaces • Naming convention for test cases • Status reporting mechanism • Regression test approach • ETVX criteria • Build/Refresh criteria {When multiple programs or objects are to be linked to arrived at single product, and one unit has some modifications, then it may need to rebuild the entire product and then load it into the integration test environment. When and how often, the product is rebuilt and refreshed is to be mentioned}. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged

puranamravinder Newbie Joined: 26Jun2008 Online Status: Offline Posts: 8	Posted: 27Jun2008 at 12:21am
	Thank you for this.... I'm really learning from this Forum.... Ravi
	http://earninglinkspuranam.blogspot.com
	IP Logged

getzephyr Groupie Joined: 25Jan2008 Online Status: Offline Posts: 47	Posted: 09Aug2008 at 12:30am
	Integration Testing: “Integration testing” is the next level of testing. This ‘level of testing’ focuses on testing the integration of “units of code” or components. Prerequisites for Integration Testing: Before we begin Integration Testing it is important that all the components have been successfully unit tested. Integration Testing Steps: Integration Testing typically involves the following Steps: Step 1: Create a Test Plan Step 2: Create Test Cases and Test Data Step 3: If applicable create scripts to run test cases Step 4: Once the components have been integrated execute the test cases Step 5: Fix the bugs if any and re test the code Step 6: Repeat the test cycle until the components have been successfully integrated
	IP Logged

tossy Groupie Joined: 20Aug2008 Online Status: Offline Posts: 99	Posted: 20Aug2008 at 3:57am
	As we covered in various articles in the Testing series there are various levels of testing: Unit Testing, Integration Testing, System Testing Each level of testing builds on the previous level. “Unit testing” focuses on testing a unit of the code. “Integration testing” is the next level of testing. This ‘level of testing’ focuses on testing the integration of “units of code” or components. How does Integration Testing fit into the Software Development Life Cycle? Even if a software component is successfully unit tested, in an enterprise n-tier distributed application it is of little or no value if the component cannot be successfully integrated with the rest of the application. Once unit tested components are delivered we then integrate them together. These “integrated” components are tested to weed out errors and bugs caused due to the integration. This is a very important step in the Software Development Life Cycle. It is possible that different programmers developed different components. A lot of bugs emerge during the integration step. In most cases a dedicated testing team focuses on Integration Testing.
	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Test Plans @ OneStopTesting

Topic: Integration Test Plan

Prerequisites for Integration Testing:

Integration Testing Steps:

How does Integration Testing fit into the Software Development Life Cycle?