AI Repair and auto-scripting
Included in free BreakTest: Claude Code or Codex can inspect a JMX, validate it, repair selectors or extractors, update JSR223 Groovy, and rerun checks through MCP/tooling.
BreakTest keeps the useful JMX foundation and moves the runtime forward: modern HTTP, lower memory pressure, AI Repair and auto-scripting, better debugging, and a far faster development loop than the upstream JMeter release cadence.
What's different
Included in free BreakTest: Claude Code or Codex can inspect a JMX, validate it, repair selectors or extractors, update JSR223 Groovy, and rerun checks through MCP/tooling.
Ask for a full script repair, or give specific instructions such as randomizing data, fixing correlation, adding pacing, or writing complex Groovy helper logic.
HTTP/2 is a first-class sampler path, preferred by default where possible. The old HttpClient 4 and Java HTTP impls are removed, keeping protocol work on one modern stack.
Leaner execution: lazy response decompression, response retention modes, shared safe test-element state, thread-local runtime state, per-thread buffers, and fewer client/reactor rebuilds.
A native Parallel Controller models browser-like concurrent requests, while the Fork Controller runs a branch of work independently from the main scripted path.
If and While Controllers support structured condition rows with all/any matching, while legacy expressions stay available for older plans.
Loop and While Controllers expose clearer index behavior, and Transaction Controllers have more explicit measurement modes for old and new JMX files.
View Results Tree surfaces what engineers actually debug: request/response details, endpoint info, HTTP/TLS metadata, cookies, variables, binary/text detection, and jump-to-source.
Boundary, CSS/HTML, Regex, XPath, XPath2, JSONPath, and JMESPath extractors can mark the sampler failed when no value is found — broken correlation becomes visible immediately.
NTLM handling on HttpClient 5, better HTTP/2 closed-session retry behavior, safer client defaults, and improved connection reuse.
Search and tree markers are improved for large plans, including clearer node handling, cleaner reset behavior, and selective removal of matched elements with confirmation.
Response decoding supports Zstandard alongside gzip, deflate, and Brotli — matching modern service compression.
BreakTest targets modern Java and uses virtual threads where they help — including virtual-user execution and embedded resource downloads.
BeanShell, BSF/JEXL2, Rhino-backed JavaScript, and LogKit are removed. JSR223 scripting focuses on Groovy — now with AI help for writing and repairing complex Groovy scripts.
Old Remote Server / RMI execution is removed. Distributed and realtime execution belongs in BreakTest Enterprise; the desktop stays simpler.
Protocol fixes, controller improvements, visual debugging, AI workflows, and resource-usage work land without waiting years for a broad upstream release.
The GUI tracks semantic test-plan edits such as add, delete, update, move, and search replace, with keyboard shortcuts and menu/toolbar state kept in sync.
JMX files with unavailable plugin elements can load with disabled placeholders and a clear notification, so teams can inspect, migrate, or repair a plan instead of hitting a hard stop.
CSV Data Set can read records in random order while preserving header behavior, and the GUI can preview the first sample variable assignments before a run.
Expected connect and response timeouts are shown as concise single-line messages, with less noisy stacktrace output in logs and View Results Tree.
Thread Groups can pace iterations directly, with clearer same-user iteration behavior and runtime variable handling when a new user iteration should start clean.
GUI validation skips artificial transaction delay and pacing sleeps, while stop/shutdown handling releases waits in ramp-up, timers, transactions, and samplers more reliably.
When BreakTest HAR metadata is available, Visual Tree and HTTP sampler editors can show recorded request/response data and cleaner recorded-vs-replayed diffs.
HTTP/2 replay removes unsupported hop-by-hop headers, improves status/request-line normalization for diffs, and tightens cookie matching so host-only cookies do not leak to unrelated hosts.
Keep the useful parts of JMeter, modernize the engine, and pair it with the BreakTest platform.