How do I turn my app's API calls into API tests?
Record them while you use the app, review the list and generate a test from the calls you keep. The Nexus Recorder in Nexus StudioQA, by Verdict System LLC, records the calls a page makes as REST or GraphQL tests, leaves auth and cookie headers out and turns secret-looking fields into environment variables. It all runs on your own machine.
Last updated:
By the Nexus StudioQA team, Verdict System LLC.
How does recording work?
- In the Nexus Recorder, record the calls the page makes while you click through a flow, such as a login and a checkout.
- Before any test is written, Review lists each call with its method, path, status, category and the reason it is in or out.
- Business, auth, read and state-changing calls start in the suite. Telemetry beacons, third-party hosts, assets and preflights start out, and you can tick any of them back in.
- Flows chain a value from one response into a later request, such as the token a login returns.
What can I generate from a recording?
- Generate test writes the API suite.
- Generate OpenAPI writes an OpenAPI 3.1 draft with types and status codes and none of the recorded values.
- Load test opens the same calls as a load plan.
What stays out of the test file?
| What the recording saw | What the test file gets |
|---|---|
| Auth and cookie headers | Left out |
| Fields with secret-looking names | An environment variable, listed under Redactions |
| JWTs, provider keys and card numbers in any field | Redacted by their value, not only by the field name |
| Telemetry, third-party hosts, assets and preflights | Out by default |
When the test runs, its auth token goes only to the origin in API_BASE_URL, never to another host that appeared in the recording.
How are the API tests judged?
They run from Patrol like any other test, and each endpoint files its own evidence folder. API tests have no sandbox: they run for real on the first press. They get API verdicts of their own: API_SECURE when every assertion held and the response shape matches the last one recorded, API_FLAKY when a retry passed, and API_DRIFTED when it passed but the shape changed, with each added, removed or retyped field named. API schema drift shows a drift on a real run.
What are the limits?
- A recording holds only the calls the page made while you recorded. An endpoint the flow never touched is not in it.
- Recording writes REST and GraphQL tests. SOAP tests are created by hand, as XML sent as text and checked with text rules.
- API tests use the Studio's own format, so moving them to another runner means rewriting them. The browser tests the Recorder writes stay standard Playwright or Selenium.
- Review the generated test before you trust it: the recording knows what the app did, not what it should do.
Where can I see it?
The Studio tour shows the Nexus Recorder, and API schema drift explains the API verdicts on a runnable example. The free trial runs the same engine on your own app.