JMeter tests depend on specific JAR packages, JMeter versions, and property configurations. Uploading these dependencies each time you create a test is repetitive and error-prone. JMeter environment management bundles them into a reusable, versioned environment that you apply to any test scenario.
With a preconfigured environment, you can:
Organize JMeter extensions and plugins across multiple test scenarios
Manage dependency files for different JMeter versions in one place
Standardize environments as templates for your team
Start new test scenarios without re-uploading dependencies
Prerequisites
Before you begin, make sure that you have:
A Performance Testing (PTS) instance
The JMeter JAR packages or property files to include in the environment
Create an environment
Log on to the PTS console and choose Performance Test > JMeter Environment.
On the Environments page, click Create Environment in the upper-right corner.
On the Create Environment page, configure the following settings:
Setting Description Environment Name A descriptive name for the environment JMeter Version The JMeter version for this environment Click Upload File to add dependency files such as custom JAR packages, CSV data files, or JMeter plugins.
NoteEach environment supports up to 80 files with a combined size of 100 MB.
(Optional) Click Upload Property File to upload a
.propertiesfile that defines JMeter runtime properties. For details, see Customize properties.Click Save.
The environment appears on the Environments page.
Modify an environment
Log on to the PTS console and choose Performance Test > JMeter Environment.
On the Environments page, find the target environment and click View in the Actions column.
On the Create Environment page, update the environment name, JMeter version, or dependency files as needed.
Copy an environment
To create a new environment based on an existing one, click Copy in the Actions column on the Environments page. The copied environment is named <Environment name>_Copy by default.
PTS provides built-in template environments with common configurations. You can view and copy template environments, but you cannot delete them.
Apply an environment to a test scenario
After you create an environment, apply it to a JMeter test scenario:
Log on to the PTS console, choose Performance Test > Create Scenario, and then click JMeter.
On the Scenario Settings tab, configure Use Dependency Environment:
Option Behavior Yes Select an existing environment. The test uses the JMeter version and dependency files from that environment. No Select only a JMeter version. Upload dependency files separately in the scenario configuration.
Customize properties
You can upload a property file to the JMeter environment to define custom properties. PTS automatically parses the property names and values, and you can edit them directly in the console.
Upload and edit properties
Log on to the PTS console and choose Performance Test > JMeter Environment.
On the Environments page, click Create Environment in the upper-right corner, or click View in the Actions column to open an existing environment.
Click Upload Property File to upload a local
.propertiesfile. PTS parses the file and displays each entry in an editable table. Modify the following fields as needed:Field Description Property Name The property key referenced in your JMX script Property Value The value assigned to the property Property Description An optional description for documentation purposes
Limits
| Item | Limit |
|---|---|
| Environments per user | 2 |
| Files per environment | 80 |
| Total file size per environment | 100 MB |