A clearer API handover
Follow the path from a contract change to reviewed checks and a useful saved result.
Loading saved sample files…
01 / Contract review
A fictional health API drops an old route and asks clients to supply a header. These are actual findings from the development engine.
Use the findings to decide what callers and checks need to change. Selected rules are covered; an empty review list does not certify compatibility.
This first example uses the original route-change fixtures. The next steps use a separate saved health-check example.
02 / Reviewed checks
In this saved IDE example, a response string changes from a minimum of 3 characters to 6. The synced suite keeps the custom check alongside the generated checks.
/fixture minimum length 3 → 6The saved sync output still requires review. It is not an automatic approval to send requests.
| Response field | Check | Expected | Origin |
|---|
Original fictional exports, including review flags and scripts retained as data. Nothing in these files is executed by this page.
03 / Saved evidence
After review, an explicit run in the development IDE produced this saved record. You are inspecting that result, not starting a new test.
Assertion flags are from the saved run. They cover this reviewed case, not every possible API behaviour.
The record ties the outcome to contract and suite revisions and stores a response hash. Reopening it does not replay the request.
A changed hash shows different bytes; it is not an automatic failure. Changed inputs need a fresh reviewed run.
Public excerpt: local run and case identifiers, environment revision, Git marker, exact time and timings were removed. Recorded outcomes, assertion flags and input/response hashes are retained.
Download evidence excerpt ↓Step 1 of 3
All API data is fictional. Contract findings were exported from the local development engine. The check exports and saved run come from the earlier tested IDE development workflow. These examples show selected behaviours, not full compatibility or release certification. Newer collection-import and local-validation additions still need native IDE acceptance.
The first step and the check/evidence steps use separate existing examples. The original check exports are review-stage files; a separately reviewed run produced the saved result. Read the sample notes ↓