All projects
backend apis
Contract tests between two services
Catch a breaking API change before it reaches the consumer.
Why it matters
Once you have more than one service, integration tests get slow and end-to-end gets flaky. Contract testing is the answer teams reach for, and few candidates have used it.
What you build
- A consumer-defined contract
- Provider verification in CI
- A deliberately broken change that gets caught
- A versioning story for the contract
If you want more
- Add a contract broker
- Gate deploys on verification
Build it
- Decide how the contract evolves without a flag day
Material for the whole build
Shows you can keep services independently deployable, which is the whole point of splitting them.
Get a plan built around projects like this