setup-contract-tests

Contract testing for microservices is set up by organizing OpenAPI and JSON Schema files in a /contracts directory, defining consumer expectations, generating mock servers, and verifying producer compliance. This Skill automates that structured setup and validation process.

Consumer-driven contract testing validates API interactions by verifying that producers meet consumer expectations defined in OpenAPI and JSON Schema. You need it to catch integration issues early and maintain compatibility across microservices before deploying to production.

OpenAPI contract validation integrates into CI/CD pipelines by running automated tests against schemas and compatibility rules using Makefile targets like test-contracts. This ensures contract loading, schema validation, and producer verification execute automatically on every code change.

Yes, event contract validation and JSON Schema verification are supported independently of REST APIs. The Skill handles both API contracts and event schemas placed under the /contracts directory, ensuring consumer expectations and schema compliance for asynchronous workflows.

The best way to generate mock servers from OpenAPI specifications is through consumer-driven testing workflows that load contracts from a central /contracts directory. This approach verifies consumer expectations against mock interactions before validating the actual producer service.

Integration tests fail despite valid OpenAPI specifications when consumer expectations and producer implementations diverge. Contract testing catches this by validating consumer-driven expectations against producer responses, ensuring schema compatibility and interaction compliance before deployment.