JMeter CLI Framework Setup
Budget: ₹600 – ₹1,500 INR
I’m looking to put a clean, command-line–driven framework around Apache JMeter so I can run consistent performance tests against our HTTP/HTTPS REST-based APIs straight from CI. The goal is a self-contained repo (or folder structure) where I can drop in new endpoints, update a few properties, and kick off a full test with one shell command.
Here’s what I need delivered:
• A scripted JMeter 5.x/CLI harness (bash or cross-platform) that downloads dependencies, spins up test runs, and stores results in time-stamped folders.
• A reusable test plan template with variables/property files so endpoints, payloads, and thread groups can be edited without touching the .jmx file.
• Automated HTML dashboard generation plus a single line summary (throughput, average latency, 95th percentile) for quick console feedback.
• Sample tests hitting at least two REST routes over HTTP and HTTPS to prove the wiring works.
• Read-me style documentation covering setup, command examples, and how to plug the framework into Jenkins or GitLab CI.
Acceptance criteria
1. I can clone the repo on a fresh machine, run one command, and see JMeter spin up, execute, and produce a dashboard.
2. Changing a URL or auth token in the properties file is all that’s required to point the test at another environment.
3. Exit codes are meaningful (non-zero on assertion failure or SLA breach) so the framework can break a CI build when performance degrades.
If you’ve built similar lightweight JMeter shells or have tips on best-practice parameterisation, I’d love to see a sample. Let’s keep the framework simple, script-only (no heavy wrappers), and focused on performance testing for APIs.
Here’s what I need delivered:
• A scripted JMeter 5.x/CLI harness (bash or cross-platform) that downloads dependencies, spins up test runs, and stores results in time-stamped folders.
• A reusable test plan template with variables/property files so endpoints, payloads, and thread groups can be edited without touching the .jmx file.
• Automated HTML dashboard generation plus a single line summary (throughput, average latency, 95th percentile) for quick console feedback.
• Sample tests hitting at least two REST routes over HTTP and HTTPS to prove the wiring works.
• Read-me style documentation covering setup, command examples, and how to plug the framework into Jenkins or GitLab CI.
Acceptance criteria
1. I can clone the repo on a fresh machine, run one command, and see JMeter spin up, execute, and produce a dashboard.
2. Changing a URL or auth token in the properties file is all that’s required to point the test at another environment.
3. Exit codes are meaningful (non-zero on assertion failure or SLA breach) so the framework can break a CI build when performance degrades.
If you’ve built similar lightweight JMeter shells or have tips on best-practice parameterisation, I’d love to see a sample. Let’s keep the framework simple, script-only (no heavy wrappers), and focused on performance testing for APIs.
Related categories:
Test Automation
Documentation
RESTful API
Continuous Integration
Bash
API Testing
JMeter
CI/CD