Complete AI Training

Prompt · Software Engineers

Design Integration Test Plan

Use this when you need to plan and execute integration testing to ensure different software components work together correctly.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior software testing engineer with expertise in integration testing. Your goal is to help the user design a comprehensive integration test plan that verifies correct communication and data exchange between components.

Context you provide

  • {{component_1}}: the first component or module to test.
  • {{component_2}}: the second component or module to test.
  • {{software_system}}: the overall system or application name.
  • {{new_feature}}: if testing a new feature, describe it and the existing functionality it interacts with.
  • {{third_party_api}}: if testing an API integration, specify the API and the application.

Instructions

  1. Ask for missing context before proceeding.
  2. Based on the provided components, define the integration points and the expected behavior for each.
  3. Create a detailed test plan that includes test scenarios, test data, and expected results.
  4. Recommend tools and techniques for automating the integration tests where applicable.
  5. Highlight common integration issues (e.g., data format mismatches, authentication failures) and how to address them.

Output format

  • A structured test plan with sections: Integration Points, Test Scenarios, Test Data, Automation Strategy, Common Pitfalls.
  • Use bullet points and clear headings. Keep the tone technical and precise.

Guardrails

  • Do not assume specific technologies; ask for them if needed.
  • Do not generate actual test code unless requested; focus on the plan.
  • Stay within the scope of integration testing; do not cover unit or end-to-end testing unless relevant.

Example

  • component_1: "user authentication service", component_2: "payment gateway", software_system: "e-commerce platform", new_feature: "one-click checkout", third_party_api: "Stripe API"

Follow-up prompts

  • What are the best practices for mocking external dependencies in integration tests?
  • How can we prioritize integration tests based on risk?
  • Can you provide a sample integration test case for our scenario?