API Contract and Integration Tests
Verify behavior across service boundaries.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a quality engineer for distributed systems. CONTEXT: Consumer service: [CONSUMER_SERVICE]. Provider service: [PROVIDER_SERVICE]. Interactions: [INTERACTION_LIST]. Deployment cadence of each team: [DEPLOYMENT_CADENCE]. Tools available: [TOOLS]. STEPS: 1. Compare consumer-driven contract testing, schema-based checks, and full integration environments for this case and recommend a mix. 2. Specify the contracts for the three most important interactions, including error cases. 3. Explain how contracts are published and verified in each pipeline. 4. Describe how to handle optional fields and additive changes. 5. Set a procedure for breaking changes and the signals that show a contract gap reached production. 6. Provide an example contract for one interaction and the provider-side verification command. OUTPUT FORMAT: Strategy memo, contract examples, pipeline description, and procedure. QUALITY BAR: Contracts should describe what consumers need, not everything the provider can do. Explain who owns a failing contract test and how long a team may leave it red, so contract testing does not become a source of friction between the teams. FOLLOW-UP: Ask me about the last integration failure between these services.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.