From Chrome DevTools cURL to an Automated Test in 60 Seconds

2026-07-17 · By Avinash Kamble, reviewed by Priyanka G.

Manual QA who capture a request in DevTools and want a repeatable test around it can skip the "read the API docs, guess the payload" step entirely.

1. Reproduce the action in the app with DevTools → Network open.
2. Right-click the request → Copy → Copy as cURL.
3. Paste into the cURL → Code Converter.
4. Pick a target (Playwright, Postman, Rest Assured, k6…).
5. Move secrets to environment variables and commit.

API docs go stale. A cURL captured from a real user session cannot be wrong — it is literally what the front-end sends. You avoid mismatched header casing, missing CSRF tokens, and undocumented required fields.

The converter automatically redacts obvious tokens (Bearer, cookies, API keys) and substitutes process.env.* placeholders. Always double-check before committing to a public repo.

Use the JSON / JSONPath / JMESPath Tester to prototype an assertion against the response, then paste it into the generated test.