Practical notes on JMeter, k6 and Gatling — recordings, correlation, migration, results files and tooling. Written from client work, not vendor decks.
Start with these
Why a bare JMeter Docker image is not enough for CI — the plugins, JDBC drivers and protocol jars have to be in the image. How to run JMeter in Docker properly, what a complete image contains, and when a pre-built multi-tool image is worth paying for.
Read moreGatling's AI converter skill, an offline multi-tool conversion, or a fixed-price human migration — how to choose a JMeter to Gatling path, fairly compared.
Read moreRun distributed JMeter on Kubernetes with StatefulSet workers and RMI done properly — plus why k6 and Gatling need different K8s primitives, not one chart.
Read moreCapture a HAR in Chrome and convert it to a JMeter JMX — free in your browser with nothing uploaded, plus what you must fix before it is a real load test.
Read moreCorrelation in JMeter: spot dynamic values, extract them with Boundary, Regex or JSON extractors, and prove the run is not silently testing nothing.
Read moreOpen a JMeter .jtl without the GUI — a free in-browser JTL file viewer that uploads nothing, what each column holds, and how to repair a broken file.
Read moreGrafana's jmeter-to-k6 converter is archived and unmaintained. Four honest options for getting JMX into k6, and the checklist to run after any conversion.
Read moreConverters handle HTTP shape well. Custom code, tool-specific samplers, deep logic, correlation intent and secrets they flag, drop or fake — and when a fixed-price review beats more automation.
Read moreDevTools cannot see a mobile app, a desktop client or a service calling an API. Fiddler, mitmproxy and JMeter's recorder can.
Read moreUse a JSR223 sampler and Groovy to write full HTTP response bodies, headers and status codes to a file in JMeter.
Read moreGenerated data can load cleanly, match its schema and pass every row count while making your load test measure the wrong thing entirely. Here are the four failures that cause it, and how to check your own data in ten minutes.
Read moreMigrated scripts can run clean, pass a linter and produce a healthy report while testing almost nothing. Here are the three failures that cause it, and how to check your own suite in ten minutes.
Read moreStay updated with the latest posts
Subscribe via RSS