Contract testing protects service boundaries from silent API drift. A consumer records the requests it sends and responses it expects; the provider verifies that it still delivers them. section 8.5.2
Parser and rendering service
A content management system sends {"markup":"# Hello"} to a rendering service and expects {"html":"<h1>Hello</h1>"}. The contract fails if a change adds, removes, reformats, or changes the meaning of response fields. section 8.5.2
Use the boundary contract to:
- Catch provider changes that break consumers before deployment. section 8.5.2
- Coordinate expectations between services, teams, or a current implementation and future AI-generated changes. section 8.5.2
- Distinguish boundary verification from integration and end-to-end tests, which validate complete system behavior. section 8.5.3






