JMeter Overview

Testable has support for executing JMeter test plans in a globally distributed fashion.

Check out the Getting Started with JMeter guide for a quick introduction on how to run your test plan.

This section of the documentation goes into further detail on the various options, environment variables, etc that we support when running a JMeter test.

• JMeter Runtime Environment
• CSV Data

Creating a JMeter Scenario

There are two ways to create a JMeter scenario:

1. Create a new Test Case (Create Test button on the dashboard or Test Cases -> New… on the left nav), select JMeter Test Plan during step 2.
2. Go to an existing test case and click on the Scenario tab. Click the New Scenario button and select JMeter as the scenario type.

Transaction vs Request

When viewing your test results you’ll notice that Testable reports metrics for transactions and requests.

There are two reasons something might be reported as a “transaction”:

1. You use a Transaction Controller in your test plan.
2. JMeter can sometimes report raw results in a hierarchy. If a sample result has children then the metrics of the parent are considered a “transaction”. For example for an http request element that requests embedded resources, it will report metrics for the total time the http request takes including loading embedded resources as well as each embedded resource time.

The reason for this is to avoid double counting metrics. For example the bandwidth reported for a transaction controller is the bandwidth used by all the individual requests. So it’s aggregated separately on Testable.

To see the raw results exactly as JMeter reports it you can add the Simple Data Writer listener to your test plan. You can run it locally or run it on Testable writing to ${__P(output_dir)}/results.jtl and you’ll see the file in the Output Files tab of the results.