Feature / API
Your UI tests already know your API.
Every click in a browser test calls your API. SmartestQA captures those calls during a run and turns them into API tests, so you do not write them by hand.
Why it matters
The API layer, tested without writing it.
- The work is already done. The requests, their order and the login are in the traffic of the test you have.
- Faster, steadier checks. API tests run without a browser and point straight at the service that broke.
- Secrets stay out. Passwords and tokens are never copied into the new test.
- captureThe calls your browser test already makes
- loginThe token is carried to the requests after it
- resultAn API test you did not have to writecreated
How it works
Capture. Pick. Run.
01
Capture
Run your browser test as usual. The calls it makes are kept.
02
Pick
Choose the calls that matter. Analytics and static files are left out for you.
03
Run
The new API test runs on every environment, with the login carried over.
FAQ
Questions about API tests from traffic.
Why turn UI tests into API tests at all?
API tests run without a browser, so they are faster and fail for fewer unrelated reasons. They also tell you which service broke.
Is this the same as converting a HAR file?
The idea is the same. Here the capture comes from a test run inside the platform, and the result lands as a test next to the UI test it came from.
Can I load test the calls I captured?
Yes. Turn them into an API test, then generate a load test from it. See Load testing with k6 and JMeter.

