JMXPress

Features

What JMXPress actually does

Everything on this page is in the product today. Where something is real but only part of the story, it says which part.

Record a journey

Capture a real user journey through a browser and turn it into a test plan, without writing one by hand.

  • Browser recording through a capture proxy on your own machine
  • Recording from a colleague’s desktop through a paired agent
  • Transaction naming and request filtering as you record
  • Optional masking of passwords, tokens and cookies in the capture

Build and convert scripts

Bring a plan from wherever it already is, or assemble one from what you have.

  • JMX Editor for reading and changing a plan in place
  • Postman collections, HAR files, cURL commands and OpenAPI specifications into scripts
  • LoadRunner and NeoLoad projects into JMX
  • JDBC script generation and test data generation
  • Correlation Helper for the values that have to be carried

Run the test

From one machine or several, with the load profile and the test data the plan actually needs.

  • JMeter, k6 and Gatling from one workbench
  • Distributed load generation across paired agents
  • Scheduled runs that start without anybody signed in
  • Network profiles, thread groups and per-agent load settings

Watch it while it runs

Client-side figures from the run, and server-side figures from the application under test, side by side.

  • Live results: samples, errors, throughput and percentiles
  • Server-side metrics from your APM, for the run’s own window
  • Saved monitoring dashboards chosen before a run starts
  • Readings only - gaps stay gaps rather than becoming zeros

APM monitoring

Connect the monitoring you already pay for, and keep what it said about each test.

  • Dynatrace, AppDynamics, Datadog, New Relic, AWS CloudWatch and Azure Application Insights
  • Credentials sealed in an encrypted store, never shown back to a browser
  • Metrics collected for the run’s window and kept with its report
  • Time ranges, refresh intervals and per-provider rate limits respected

Reports that outlive the run

What happened, in a form you can send to somebody who was not watching.

  • Report generation from a results file, with charts and tables
  • Comparison reports across runs
  • JTL Analyzer and JTL Editor for the raw results
  • APM metrics report for the run’s monitored window

Diagnostics

When a run shows a problem inside the application rather than in front of it.

  • Thread dumps and heap dumps collected from a paired computer
  • Heap, thread and memory analysis of what was collected
  • Application log collection from folders that machine allows
  • Opt-in on the machine itself - never something a web page can take

Built for a team

More than one person, more than one project, and a record of who did what.

  • Organisations, with every tenant’s data isolated in the database itself
  • Roles and capabilities rather than one kind of user
  • Projects with plans, environments, variables and run history
  • An audit trail of account and access changes

Where to read more

The documentation covers each of these step by step, with the pages and the settings named as they appear in the application.

Open the documentation Ask us something