@edgetesting/jmeter

CLI wrapper that uploads JMeter .jtl result files to EdgeTesting, evaluates SLA thresholds, and automatically creates Jira bug reports on violations.

Requirements

• Node.js 18+
• Apache JMeter (for running tests)
• An EdgeTesting workspace with an API key

Installation

npm install -g @edgetesting/jmeter

# Or use without installing
npx @edgetesting/jmeter --help

Quick start

# 1. Run your JMeter test
jmeter -n -t my-test-plan.jmx -l results.jtl

# 2. Upload results with a 500ms SLA
npx edgetesting-jmeter --file results.jtl --id TC-100 --sla 500

Options

| Flag | Required | Description | |---|---|---| | --file <path> | yes | Path to the .jtl file (CSV or XML) | | --id <automation_id> | yes | EdgeTesting automation ID, e.g. TC-100 | | --sla <ms> | no | Latency SLA in ms — bug created if avg or P95 exceeds this | | --sla-error-pct <n> | no | Error rate SLA — bug created if error % exceeds this | | --issue <jira_key> | no | Override the Jira issue key on the test case | | --api-key <key> | no | API key (or set EDGETESTING_API_KEY) | | --api-url <url> | no | Base URL (or set EDGETESTING_API_URL) | | --dry-run | no | Parse and print metrics locally, no upload |

Environment variables

EDGETESTING_API_KEY=et_xxxx
EDGETESTING_API_URL=https://your-edgetesting-instance.com

Metrics extracted

• Average latency (ms)
• P95 and P99 latency (ms)
• Min / Max latency
• Throughput (requests/sec)
• Error percentage
• Per-endpoint breakdown

SLA violations

When a threshold is breached the CLI:

• Creates a Bug Report in EdgeTesting
• Posts a Markdown metrics table as a Jira comment
• Exits with code 1 to fail your CI build

Severity is derived automatically based on how far the result exceeds the threshold.

Supported .jtl formats

• CSV — default JMeter output (timeStamp,elapsed,label,success,Latency,...)
• XML — standard JMeter XML with <httpSample> / <sample> elements

License

MIT