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: How to write an Integration Test Case?

Post Reply Post New Topic
Author Message
soumali
Newbie
Newbie
Avatar

Joined: 02Apr2007
Online Status: Offline
Posts: 34
Quote soumali Replybullet Topic: How to write an Integration Test Case?
    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)




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

IP IP Logged
JustinH
Newbie
Newbie
Avatar

Joined: 28Jul2009
Location: United States
Online Status: Offline
Posts: 13
Quote JustinH Replybullet 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

and

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




Edited by JustinH - 22Sep2009 at 2:11am
- Justin
___________________________
Founder and CEO of Hexawise
www.hexawise.com
"More coverage. Fewer tests."
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 10.836 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