07 / Test the behavior
Test complete API behavior, not just whether one request returned 200
Send requests, carry data across steps, validate response behavior, and keep the evidence needed to understand a failure.
4 / 4 assertions486 ms
- ✓Status is 201
- ✓Content-Type is JSON
- ✓Schema matches contract
- ✓id is present
Working reference
What goes in, what comes out, and what the result can prove.
Concrete artifact
Test behavior around the success path
201 create → validate Location header
409 duplicate → validate stable error code
401 missing token → validate challenge
429 burst → validate Retry-AfterReview sequence
Three checks before the result becomes a decision.
Positive behavior
Verify the expected payload and headers, not only status.
Negative behavior
Exercise authentication, validation, conflict and rate limits.
State transitions
Confirm that dependent requests observe the intended change.
Limits
What this workflow does not prove.
- Coverage is limited to the inputs, states and assertions you define.
- Tests against mocks and tests against real integrations answer different questions.
- Flaky environments should be diagnosed, not normalized with unlimited retries.
Questions worth answering
Before you put it into a real workflow.
Can I import cURL?
Yes. Import a cURL command to populate the request and continue from there.
Can tests span multiple endpoints?
Yes. Multi-step flows can extract and reuse values across requests.
Can I test negative cases?
Yes. Expected errors, invalid inputs, authorization failures, and edge cases should be modeled as explicit test cases.
Next move
Start with one concrete API problem.
Keep the first step small. Move into a workspace when the result deserves to be saved, repeated, or shared.