api-contract-testing

Contract testing verifies that APIs honor their contracts between consumers and providers. It ensures that service changes don't break dependent consumers without requiring full integration tests. Contract tests validate request/response formats, data types, and API behavior independently. Minimal working example: Detailed implementations in the references/ directory: - Overview - When to Use - Quick Start - Reference Guides - Best Practices - Testing microservices communication - Preventing breaking API changes - Validating API versioning - Testing consumer-provider contracts - Ensuring backward compatibility - Validating OpenAPI/Swagger specifications - Testing third-party API integrations - Catching contract violations in CI - Test contracts from consumer perspective - Use matchers for flexible matching - Validate schema structure, not specific values - Version your contracts - Test error responses - Use Pact broker for contract sharing - Run contract tests in CI - Test backward compatibility - Test business logic in contract tests - Hard-code specific values in contracts - Skip error scenarios - Test UI in contract tests - Ignore contract versioning - Deploy without contract verification - Test implementation details - Mock contract tests