Contract testing: Test strategy and fixtures
Consumer expectations, including authentication and error shapes, are verified against the real provider in CI before merge; HTTP status codes cannot be mocked away on either side of the contract.
Flaky tests enter an owned quarantine record with deadline and retry budget; required CI gates stay honest by reporting quarantined failures separately instead of silently turning green.