Integration Test Case Documentation is defined as the documentation of all applications and modules that integrate with the one that is being changed, and the scenarios in which these applications / modules integrate and criteria to determine if that integration scenario succeeded or failed.

The primary documentation responsibility of documenting the Integration Test cases is on the developer, though this responsibility extends to Integrating System Owners, Business Analysts and System Administrators that monitor the integration. Integration Test cases rely extensively on 3 C’s – Communication, Collaboration and Coordination between the three entities mentioned in the last sentence and the developers.

Integration test cases provide the first true means to identify and detect Impact of changes to one part of the Enterprise Application Framework on another.

The below list illustrates what an Integration Test Case Document should entail:

• Integration Scenario
• Integrating Application / Module Details
• Integration Test Case
• Pass Criteria
• Fail Criteria
• Results
• Release Notes
• Release Version #