API Workflow Tester
Verify state and data integrity across documented API transitions.
Inputs and evidence
Require the workflow requirement or contract, documented states and transitions, actors,
operations or events, and available persistence or event evidence. Mark undocumented timing,
terminal states, and side effects Not specified.
Workflow
- Map starting state, allowed transitions, actors, calls, events, and terminal outcomes.
- Trace IDs, correlation values, and data dependencies passed between steps.
- Define response and persisted-state assertions after each transition.
- Define polling, callback, or event checks using only documented timing and terminal states.
- Add negative transition cases and safe compensating cleanup for owned test resources.
- HUMAN REVIEW GATE (mandatory). Confirm the sequence, side effects, test identities,
environment, and cleanup before writing automation or invoking any operation.
Output shape
| Step |
State before |
Call or event |
Expected state |
Evidence |
Cleanup |
Include prerequisites, correlation map, unresolved requirements, and review decision.
Guardrails
- Never invent a state, transition, callback, timeout, event, or consistency window.
- Never assume a successful response proves a downstream state change; require evidence.
- Use synthetic, uniquely identified records and redact credentials and sensitive data.
- Do not execute against a live system without explicit authorization, environment scope,
request limits, and ownership of every resource that may be changed or removed.
1---2name: api-workflow-tester3description: Design stateful tests spanning multiple API calls, lifecycle transitions, asynchronous jobs, events, or callbacks. Use when asked to test an end-to-end API workflow, chain endpoints, verify a resource lifecycle, or validate eventual outcomes. Produce a cross-operation sequence with state evidence and cleanup, not a single-endpoint matrix.4license: MIT5---67# API Workflow Tester89Verify state and data integrity across documented API transitions.1011## Inputs and evidence1213Require the workflow requirement or contract, documented states and transitions, actors,14operations or events, and available persistence or event evidence. Mark undocumented timing,15terminal states, and side effects `Not specified`.1617## Workflow18191. Map starting state, allowed transitions, actors, calls, events, and terminal outcomes.202. Trace IDs, correlation values, and data dependencies passed between steps.213. Define response and persisted-state assertions after each transition.224. Define polling, callback, or event checks using only documented timing and terminal states.235. Add negative transition cases and safe compensating cleanup for owned test resources.246. **HUMAN REVIEW GATE (mandatory).** Confirm the sequence, side effects, test identities,25 environment, and cleanup before writing automation or invoking any operation.2627## Output shape2829| Step | State before | Call or event | Expected state | Evidence | Cleanup |30|---|---|---|---|---|---|3132Include prerequisites, correlation map, unresolved requirements, and review decision.3334## Guardrails3536- Never invent a state, transition, callback, timeout, event, or consistency window.37- Never assume a successful response proves a downstream state change; require evidence.38- Use synthetic, uniquely identified records and redact credentials and sensitive data.39- Do not execute against a live system without explicit authorization, environment scope,40 request limits, and ownership of every resource that may be changed or removed.
PramodDutta