🚀
HTTP/2 & HttpClient 5
HTTP/2 is first-class and the old duplicated HTTP client paths are removed — one modern stack.
Free desktop & runtime
BreakTest
A modern, JMeter-compatible fork for engineers who like the JMX workflow but need active development, current protocols, lower resource usage, and far better script feedback. AI Repair is fully supported in the free download, so Claude Code or Codex can help fix and improve your plans locally.
Based on JMeter 5.6.3. Your JMX files and most plugins keep working.
Screenshot: BreakTest GUI
Test plan + visual results tree
Based on JMeter 5.6.3
Java 21+ runtime
JMX compatible
HTTP/2 first
AI Repair included free
Modernized JMeter workflow
Significant improvements
The familiar test-plan model — with a faster, lighter, more debuggable engine underneath.
⚡
Lower memory usage
Lazy decompression, response retention modes, lightweight cloning, and per-thread buffers cut pressure during large tests.
🤖
AI Repair & auto-scripting
Use Claude Code or Codex through MCP/tooling to inspect, repair, validate, and rerun your JMX automatically.
🧩
Better controllers
Parallel and Fork controllers model realistic browser concurrency and independent work branches, while If/While conditions are easier to build and review.
🔍
Improved Visual Tree
HTTP/TLS metadata, request/response detail, variables, cookies, binary/text detection, and jump-to-source.
🧹
Less legacy
Groovy-focused scripting, Java 21+, virtual threads, Zstandard support, and removed RMI Remote Server.
↶
Undo and redo
Semantic GUI history for add, delete, update, move, and search replace operations makes large plan editing less fragile.
📦
Missing plugin placeholders
Open JMX files even when plugin elements are unavailable, then inspect disabled placeholders and decide how to migrate.
🎲
Random CSV data and preview
Randomize CSV Data Set records and preview the first variable assignments before running the test.
⏱
Better pacing and timing
Thread Group pacing, loop index options, and clearer transaction measurement modes make runtime behavior easier to express.
■
Cleaner stop and validation runs
Validation avoids artificial sleeps, and shutdown releases ramp-up, timer, transaction, and sampler waits more reliably.
⌘
Instruction-driven script changes
Ask for a full script repair or targeted changes like randomizing data, fixing correlation, or writing complex JSR223 Groovy scripts.
See it work
Debugging that actually helps.
The View Results Tree now surfaces what performance engineers really debug — so you stop bouncing between logs and raw samples.
- Failed extractors can fail the sampler instantly
- Endpoint, TLS, and timing detail in one place
- Recorded HAR request/response views help compare conversion output
- Cleaner timeout errors keep expected failures readable
- Structured controller conditions make branching logic easier to inspect
- AI Repair can fix broken scripts and JSR223 Groovy logic from your instructions
- Jump straight to the offending test element
GIF: visual debugging
Results tree / AI script repair
Compatibility
Familiar, but not frozen.
JMX files still matter
- Existing JMeter JMX files keep working for common test plans.
- Most plugins work when they don't depend on removed internals.
- Legacy saved values are mapped where practical.
- A new
BreakTest JMXunlocks the features JMeter has no equivalent for.
Honest reality check
- Old HTTP impls, BeanShell, BSF/JEXL2, Rhino JS, LogKit, and Remote Server are removed.
- Backwards compatibility can be fragile around plugins hooking legacy classes.
- The goal is a better tool — not preserving every old edge case forever.
- For scale, use BreakTest Enterprise instead of old Remote Server workflows.
Use BreakTest locally for free.
Build, repair with AI, and run scripts on your machine. Move to Enterprise when those same scripts need private, distributed scale.