Apache JMeter CLI Editor
A CLI Editor which allows you to open, edit and create JMX files. Ideal for quick adjustments to an existing test.
£29 one-time – 3 seats / users / machines
What's Included
Demo
Overview
The Apache JMeter CLI Editor is a powerful command-line tool that lets you work with JMeter test plans without launching the full GUI. Perfect for quick edits, automation pipelines, and headless environments.
3 Seats Included
Your purchase includes 3 device licenses — install on your laptop, CI server, and a colleague’s machine at no extra cost.
Two Modes of Operation
Interactive TUI Mode
jmeter-edit test.jmx # Open file in interactive terminal editor
A full terminal UI for browsing and editing your test plan visually.
Batch Mode
jmeter-edit set test.jmx "Test Plan/Thread Group" ThreadGroup.num_threads 50 --save
Script your changes for CI/CD pipelines and automation workflows.
CLI Batch Commands
In addition to the interactive TUI, JMeter CLI Editor provides batch commands for scripting and automation:
jmeter-edit list <file> # List tree structure
jmeter-edit get <file> <path> # Get element properties
jmeter-edit set <file> <path> <prop> <val> # Set property value
jmeter-edit add <file> <parent> <type> # Add new element
jmeter-edit delete <file> <path> # Delete element
jmeter-edit enable <file> <path> # Enable element
jmeter-edit disable <file> <path> # Disable element
jmeter-edit export <file> # Export to JSON
Tree Path Format
Elements are identified by /-delimited paths using their testname:
"Test Plan" # Root element
"Test Plan/Thread Group" # Child element
"Test Plan/Thread Group/HTTP Request[0]" # First when duplicates exist
"Test Plan/Thread Group/HTTP Request[1]" # Second when duplicates exist
CLI Examples
# List tree structure
jmeter-edit list test.jmx
jmeter-edit list test.jmx --depth 2 --show-properties
# Get element properties
jmeter-edit get test.jmx "Test Plan/Thread Group"
jmeter-edit get test.jmx "Test Plan/Thread Group" -p ThreadGroup.num_threads --json
# Set property and save
jmeter-edit set test.jmx "Test Plan/Thread Group" ThreadGroup.num_threads 100 --save
jmeter-edit set test.jmx "Test Plan/Thread Group" --name "API Users" --save
# Add new element
jmeter-edit add test.jmx "Test Plan/Thread Group" HTTPSamplerProxy --name "Login Request" --save
jmeter-edit add test.jmx "Test Plan/Thread Group" ConstantTimer -p ConstantTimer.delay=1000 --save
# Enable/disable elements
jmeter-edit disable test.jmx "Test Plan/Debug PostProcessor" --save
jmeter-edit enable test.jmx "Test Plan/Debug PostProcessor" --save
# Delete element
jmeter-edit delete test.jmx "Test Plan/Thread Group/View Results Tree" --save
# Export to JSON
jmeter-edit export test.jmx --flatten --include-properties -o export.json
Global CLI Options
| Option | Description |
|---|---|
--version | Show version number |
--licenses | Show third-party licenses |
--json | Output in JSON format |
--save | Save changes to input file |
-o FILE | Save to specified file |
-q, --quiet | Suppress non-essential output |
Command-Specific Options
| Command | Option | Description |
|---|---|---|
set | --type TYPE | Property type: stringProp, boolProp, intProp, longProp |
set | --enabled true/false | Enable or disable element |
set | --name NAME | Rename the element |
add | --list-types | List all available element types |
add | -p KEY=VALUE | Set property (repeatable) |
Use jmeter-edit <command> --help for detailed command options.
CI/CD Integration
Batch update multiple test files in your pipeline:
# Update thread counts across all test files
for f in *.jmx; do
jmeter-edit set "$f" "Test Plan/Thread Group" ThreadGroup.num_threads 100 --save
done
# Disable debug samplers before production run
for f in *.jmx; do
jmeter-edit disable "$f" "Test Plan/Debug Sampler" --save 2>/dev/null || true
done
# Export all test plans to JSON for documentation
for f in *.jmx; do
jmeter-edit export "$f" --flatten -o "${f%.jmx}.json"
done
Key Benefits
Speed & Efficiency
Make rapid adjustments to your JMX files without waiting for the JMeter GUI to load. Ideal for CI/CD pipelines and scripted workflows.
Cross-Platform Support
Available for:
- Linux (x86_64)
- Windows (x86_64)
Lightweight
Minimal resource footprint - runs efficiently on any machine without the overhead of a graphical interface.
Why CLI Editor?
| Need | Without CLI Editor | With CLI Editor |
|---|---|---|
| Change thread count / ramp-up | Launch full JMeter GUI (slow) | One command, <5 seconds |
| Batch update 20+ JMX files | Manual or fragile scripts (error-prone) | Scriptable, safe edits in loop |
| Edit on headless Linux server | Impossible without X forwarding | Native binary, zero GUI deps |
| CI/CD parameterization | Property files only (limited) | Direct JMX patching + version control |
The Investment
£29 one-time for 3 seats — under £10 per user. No recurring fees like enterprise JMeter cloud platforms.
Cheaper than one hour of a senior performance engineer’s time, yet it pays for itself after a handful of batch edits or pipeline tweaks.
Use Cases
- Quick modifications to thread counts, durations, or endpoints
- Batch editing multiple JMX files in CI/CD pipelines
- Remote server management where GUI isn’t available
- Scripted test plan generation and modification
- Exporting test structure for documentation or analysis
What’s Included
- 3 device licenses — laptop, CI server, colleague
- CLI Editor executable for your chosen platform
- Full batch mode command reference
- Free updates within the major version
- 30-day money-back guarantee — if the product doesn’t meet your expectations, email us within 30 days of purchase for a full refund (no questions asked)
After Purchase
After completing your purchase, you’ll receive an email from LemonSqueezy containing your license key. Use this key to:
- Download the software — Visit the download page and enter your license key
- Activate the application — Enter your license key when prompted on first run
- Check for updates — The app will automatically notify you when updates are available