Overview
Contract tests check the expectations shared between a consumer and a provider. They are useful when a PHP application integrates with internal services or third-party APIs that can change independently.
Define the contract
Record required fields, types, status codes, authentication behavior and error responses. Include optional fields and compatibility rules so consumers do not accidentally depend on undocumented details.
Test both sides where possible
Consumer tests verify what the client expects. Provider verification checks that the service still satisfies those expectations. For external providers, use documented schemas and controlled fixtures when provider verification is unavailable.
Keep fixtures trustworthy
Fixtures should represent documented examples or captured, sanitized responses. Do not store real personal data, tokens or production secrets in test files.
Avoid confusing contract and end-to-end tests
A contract test checks compatibility at a boundary; it does not prove the entire distributed workflow succeeds under production conditions.