Star on GitHubMulti-Step API Testing Flows
Build multi-step API tests that chain requests with auto-mapped variables. Import real browser traffic, add assertions between steps, and export YAML for Git review and CI/CD pipelines.
Build multi-step API tests in four steps
Record real traffic, chain requests with auto-mapped variables, export to YAML, and run end-to-end API tests in CI.
1. Capture API traffic from your browser
Record a HAR from Chrome DevTools or a proxy and import it. DevTools parses every request, header, and auth token automatically.
- • Chrome DevTools → Save all as HAR
- • Sensitive data safe: process happens locally
2. Chain requests with auto-mapped variables
DevTools extracts tokens and IDs from responses and maps them to subsequent requests. Fine‑tune variable passing with JSONPath‑based overrides.
- • Auto‑mapped variables from responses
- • Override rules per step
3. Build multi-step test flows visually
Use a visual canvas to organize API requests, add assertions, and set dependencies between steps. Export clean YAML for code review.
4. Export YAML and run API tests in CI
Export human-readable YAML for Git review, then run end-to-end API tests in CI with parallel execution, JUnit reports, and clear exit codes.
- • Git‑reviewable flow definitions
- • CLI reports (JUnit/JSON, exit codes)
