Print Page | Close Window

How to write an Integration Test Case?

Printed From: One Stop Testing
Category: Types Of Software Testing @ OneStopTesting
Forum Name: Integration Testing @ OneStopTesting
Forum Discription: Discuss All that is need to be known about Integration Software Testing and its Tools.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=1496
Printed Date: 30Nov2024 at 7:23am


Topic: How to write an Integration Test Case?
Posted By: soumali
Subject: How to write an Integration Test Case?
Date Posted: 13Jun2007 at 12:58am
How to write an Integration Test Case:

Simply put, a Test Case describes exactly how the test should be carried out.
The Integration test cases specifically focus on the flow of data/information/control from one component to the other.

So the Integration Test cases should typically focus on scenarios where one component is being called from another. Also the overall application functionality should be tested to make sure the app works when the different components are brought together.

The various Integration Test Cases clubbed together form an Integration Test Suite
Each suite may have a particular focus. In other words different Test Suites may be created to focus on different areas of the application.

As mentioned before a dedicated Testing Team may be created to execute the Integration test cases. Therefore the Integration Test Cases should be as detailed as possible.

Sample Test Case Table:

Test Case ID

Test Case Description

Input Data

Expected Result

Actual Result

Pass/Fail

Remarks

 

 

 

 

 

 

 

Additionally the following information may also be captured:
a) Test Suite Name
b) Tested By
c) Date
d) Test Iteration (One or more iterations of Integration testing may be performed)



Replies:
Posted By: JustinH
Date Posted: 22Sep2009 at 2:09am
Too often, sets of integration tests are much less effective than they should be because, when considered as a whole, they both (a) cover the same combinations of variables multiple times (and therefore waste time that could be better spent elsewhere) and (b) accidentally forget to test for common combinations that should be tested (and therefore risk defects not being detected).

More information on this topic is available at: http://hexawise.wordpress.com/2009/09/18/efficient-and-effective-test-design - http://hexawise.wordpress.com/2009/09/18/efficient-and-effective-test-design / 

and

http://www.combinatorialtesting.com/clear-introductions-1 - http://www.combinatorialtesting.com/clear-introductions-1

I've helped build a tool (with a free version available) to solve both of these problems.  It is available to anyone who wants to sign up for it at: http://www.hexawise.com/users/new - http://www.hexawise.com/users/new




-------------
- Justin
___________________________
Founder and CEO of Hexawise
www.hexawise.com
"More coverage. Fewer tests."


Print Page | Close Window