Blog
How to get a k6 or JMeter load test from API test steps
A functional API test already holds what a load test needs: the requests, their order, and the values passed from one response to the next. SmartestQA builds a k6 script or a JMeter plan from those steps when you describe the load in a sentence.
The problem
A functional API test and a load script describe the same journey. Log in, take the token, create an order, read it back. One runs it once and checks the answers. The other runs it many times at once and measures how long the answers take.
Yet the two are often written separately, in different tools, by different people. The load script is created before a release and then goes stale as the API changes.
How SmartestQA does it
Keep one source, the functional steps, and derive the load test from it whenever the journey changes.
- Say the load in words. Users, ramp-up and think time, in a sentence.
- k6 or JMeter. Generate either, or bring the scripts you already have. The file stays yours.
- Same pipelines, same report. Load tests run next to your functional tests.
- A comparison, not just charts. Each run is set against the previous one: better, worse or similar.
Questions and answers
Should I choose k6 or JMeter?
Choose the one your team can read and maintain. SmartestQA generates, edits and runs both.
Can I reuse functional tests as load tests?
API-level tests, yes: they carry the requests, the order and the data flow a load test needs.
How do I know a slowdown is real?
Compare like with like. The report compares each run with the previous one and warns when the load was not the same.
Where to read more
See Load testing with k6 and JMeter, or the documentation: Load test steps.

