| name | activity-contract-test-design |
| description | Design consumer/provider contract and schema-compatibility tests from a spec or story. Use when deriving contract test strategy during black-box testing. |
Activity: Contract Test Design
Generate consumer/provider contract test strategies and schema compatibility checks from a specification or user story. Produces contract validation scenarios that ensure API boundaries, data schemas, and inter-service agreements are honored. Invoked by the verifier agent in Design Mode.
RFC 2119 Notice: The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in RFC 2119.
Goal
Derive contract-level test scenarios that validate API boundaries, data schemas, and inter-service agreements from the outside. Contract tests verify that providers deliver what consumers expect, without coupling to internal implementation.
Context
This activity assumes:
- A numbered list of acceptance criteria is available (produced by Phase 2 of
verifier).
- API endpoints, data entities, and integration points have been identified from the source artifact.
- The output feeds into the contract section of the test plan assembled by
verifier.
Process
- Identify contracts. Extract every API endpoint, event/message schema, and inter-service boundary from the source artifact.
- Classify contract type:
