Readiness

Validation Engine

Schema validation says a payload is well-formed; this says it is correct. Author business-rule assertions over your scenarios, see response-flow coverage, and orchestrate the failure scenarios you are missing.

Readiness Scorecard
Engine
Contract & resilience
Contract
46blocked
Resilience
46blocked
Endpoints
4
Scenarios
2
Rules
0

2/4 endpoints covered (50%) · 6 coverage gaps across response, error, business-rule and test-data dimensions.

3 unsafe-method endpoints · 0 list endpoints · 7 resilience gaps (idempotency, retry/back-off, rate-limit, pagination, failure coverage).

Open full scorecard
Analytics
Coverage by dimension

Endpoint = has ≥1 scenario · response/error = declared status codes with a scenario · failure = critical endpoints with a timeout/downstream scenario.

Analytics
Scenario kinds

Distribution of scenario kinds — a healthy suite spans happy, validation, auth and failure paths.

Coverage
Response-flow coverage matrix
Scenarios →
Endpoint200201202400401404409503
POST/orders
·✓·○○·○·
GET/orders/{id}
○····○··
PATCH/orders/{id}
○··○··✓·
POST/orders/{id}/fulfill
··○···○○
Assertions
Business-rule builder
0 rules
New assertion
When
Then
No business-rule assertions yet

Schema validation can't say which input yields which outcome. Encode a rule like ‘WHEN scenario kind is validation_error THEN status class is 4xx’ to assert business semantics over your scenarios.

Resilience
Failure-scenario orchestration
POST/orders4 proposals
  • Upstream timeout504

    Dependency/timeout failures are common in microservice meshes yet routinely under-tested.

  • Downstream dependency failure503

    Prove the endpoint degrades predictably when a downstream service is unavailable.

  • Rate-limit response429

    Exercise the 429 path so clients and agents can verify their back-off handling.

  • Auth rejection401

    Confirm protected endpoints reject missing/invalid credentials with a stable shape.

GET/orders/{id}4 proposals
  • Upstream timeout504

    Dependency/timeout failures are common in microservice meshes yet routinely under-tested.

  • Downstream dependency failure503

    Prove the endpoint degrades predictably when a downstream service is unavailable.

  • Rate-limit response429

    Exercise the 429 path so clients and agents can verify their back-off handling.

  • Auth rejection401

    Confirm protected endpoints reject missing/invalid credentials with a stable shape.

PATCH/orders/{id}3 proposals
  • Upstream timeout504

    Dependency/timeout failures are common in microservice meshes yet routinely under-tested.

  • Rate-limit response429

    Exercise the 429 path so clients and agents can verify their back-off handling.

  • Auth rejection401

    Confirm protected endpoints reject missing/invalid credentials with a stable shape.

POST/orders/{id}/fulfill4 proposals
  • Upstream timeout504

    Dependency/timeout failures are common in microservice meshes yet routinely under-tested.

  • Downstream dependency failure503

    Prove the endpoint degrades predictably when a downstream service is unavailable.

  • Rate-limit response429

    Exercise the 429 path so clients and agents can verify their back-off handling.

  • Auth rejection401

    Confirm protected endpoints reject missing/invalid credentials with a stable shape.