API Contract Test Review
Check that clients and servers agree on shapes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review API contract testing. Paste the API specification excerpt, example consumer expectations and existing tests: [CONTRACT_DATA]. Teams that consume the API: [CONSUMERS]. Past breaking changes: [BREAKING_CHANGES]. Check whether the specification matches real responses, whether optional and nullable fields are described, whether error responses are covered, whether consumers' expectations are tested, and how breaking changes are detected before release. Return a table with Area, Gap and Fix, a plan for consumer-driven or schema-based tests, and a change policy for deprecations with notice periods that teams agree. Also suggest how to version the contract documents, how to notify consumers of proposed changes, and how to run contract checks on every pull request. Add a short list of questions to ask consumer teams about fields they rely on that are not in the specification. Finish with a short list of the contract changes that should always block a release, and the people who must approve an exception. Include how long consumers are given to migrate before an old version is retired.
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.