This guide walks through testing an API end-to-end, from your first request to a suite running automatically in CI.
- 1
Bring in your requests
Start from an OpenAPI/Swagger spec, a Postman collection, a cURL command, or build requests manually. See the Request Builder overview for all four import paths.
Request Builder - 2
Add assertions
Check status codes, response timing, and specific fields in the payload — not just "did it return 200".
Assertions - 3
Chain related requests
Test real flows — sign up, log in, create a resource, verify it — by chaining requests and passing values between steps.
Request Chaining - 4
Check the edges, not just the happy path
Add boundary and negative cases: invalid input, missing auth, rate limits. See the boundary testing guide for a checklist.
Boundary Testing for APIs - 5
Run it in CI
Wire your suite into your pipeline so every pull request runs it automatically, not just your local machine.
Run Testing from CI/CD
Placeholder content
This is dummy copy scaffolded for the migration — expand each step with real screenshots and examples before publishing.