Converting what you already have#
If the journey is already described somewhere — a Postman collection, a HAR file, an API specification, an old LoadRunner script — you do not have to record it again.
All of these are under Utilities.
What can be converted#
| From | Page | Notes |
|---|---|---|
| Postman collection | Postman Script Generator | Requests, headers, bodies and variables |
| HAR file | HAR Script Generator | A browser's own recording of a session |
| cURL command | cURL to JMX | One request, pasted as the command line |
| OpenAPI / Swagger | Swagger to JMX | Read as YAML or JSON |
| LoadRunner | LR to JMX | The script's requests and transactions |
| NeoLoad | NeoLoad to JMX | From an exported project |
| SQL / JDBC | JDBC Script | A plan that exercises a database directly |
Each produces a JMeter plan you can run, save into a project, or open in the JMX Editor.
Note A conversion is a starting point, not a finished test. Anything that was dynamic in the original — a session token, an id returned by a previous call — needs correlating before the plan will run more than once. See below.
Correlation#
A recorded or converted plan replays exactly what happened once. The second time, the server issues a different session id and the plan sends the old one.
Utilities → Correlation Helper finds values that appear in one response and are sent in a later request, and shows you the extractor that would carry them. That is the work that turns a captured journey into a test that runs repeatedly.
Test data#
Utilities → Test Data Generation makes CSV files to drive a plan — names, emails, numbers, dates, and values from a list — so a test is not a thousand users all called the same thing.
Bind the result to the plan's dataset in its project.
Editing a plan directly#
Utilities → JMX Editor opens a plan as a tree: thread groups, samplers, timers, assertions, the lot. It is for the change you do not want to make by hand in XML — renaming a transaction, adjusting a timer, switching an assertion.
Other engines#
JMXPress generates scripts for k6 and Gatling from the same material, not only JMeter. The engine is chosen where the script is generated.
Note JMeter is the engine everything is built around: recording produces a JMeter plan, and the converters target JMX. k6 and Gatling scripts are generated from the same captured material.