Menu

1 / 2

Contract testing without the tests

DEV Community: microservices·Graphwake·about 5 hours ago
#OGvQWz0D
#devtomicroservices#devto#dev#spec#teams
Long article (1278 words) — no AI summary yet.
Reading 0:00
15s threshold

Cross-team integrations break at the seams. Each service passes its own tests, and then the two stop agreeing. Contract testing is the usual answer, and most rollouts stall before every consumer has written its tests.

We build Graphwake , which tells the teams that consume an API when a change in its OpenAPI spec is about to break them, and we built it around a smaller ask: the OpenAPI spec you already publish, plus one subscription from each team that calls an endpoint. That catches the common breaking changes on every endpoint. It doesn't replace tests where behaviour matters, and we'll come back to where those still pay off.

Why adoption stalls

Pact describes itself as "a code-first tool for testing HTTP and message integrations using contract tests", and its contract "is generated during the execution of the automated consumer tests" ( docs.pact.io , as of 2026-11-14). That's where the cost comes from, and the people who pay it aren't the people who change the API.

The consumer pays.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.