Contract tests, visualised.
Validate that apps work together using the tests you already have. Less boilerplate, more signal.
What you need to run a Contract Test
To verify a contract, choose the application and its version, pick the environment you want to check (dev, staging, or prod), and set the point in time to compare against.
We use your existing interactions to validate expectations across versions and environments.
Reuse the tests you already have
Promote interactions captured in existing tests into versioned contracts across teams.
Clear, high‑level results across protocols
See at a glance whether contracts pass or fail across HTTP and Kafka, all in one view. Quickly spot which areas are healthy and where to drill in.
Protocol‑aware summaries roll up results so teams can align fast.
Drill in to compare at every level.
Start from high‑level protocol summaries and click through to services, endpoints, and individual interactions. Compare payloads, headers, timing, and even field‑level differences across versions and environments.
From overview to detail in a couple of clicks.
See exactly where things fail. In a diagram.
Failures are visual: red and amber highlights and markers show which interactions broke and where, so you can spot issues at a glance.
Tap a highlighted interaction to inspect the request and response and compare them with the expected contract.
Kafka, too — same clarity.
Get the same visual diffs for Kafka: see failing topics, partitions, and messages at a glance, then drill into payloads, headers, keys, and timing to understand exactly what changed.
Protocol‑aware views make streaming contracts as clear as HTTP.
Drill right down to the data.
When something doesn’t match the contract, you can still drill in to the exact request and response data that caused the result — body, headers, status, timing, and more.
Understand the why behind every pass or fail.
Pipeline API
Stop pushing out applications that don't work together by using the API to give a fast response.