Import your JMeter test

JMeter is an open source load testing tool capable of recording HTTP requests via a built–in HTTP proxy. The JMX file is a saved JMeter script in XML format. PFLB Platform supports JMX files import.

To create a test based on the JMeter script, follow these steps:

1. Create the script in JMeter.

2. Import the script in PFLB Platform.

3. Edit a load profile.

4. Add SLAs.

5. Link a settings set.

To upload tests from PFLB Platform and edit them in Apache JMeter, you can use a special plugin.

For more information about limitations of PFLB Platform when working with JMeter scripts, see Supported plugins and elements of JMX scripts.

Record a script

To create a script in JMeter, use the Apache JMeter documentation.

Import a script

1. In the upper menu, click + New Test.

2. In the Import data pane, click Import from JMeter. The dialog opens:

   

3. To upload a JMX file, click and select it, or drag and drop the file from the local folder to JMX file upload area. The file size should not exceed 100 MB.

4. Upload any supporting files that the script uses, as you did in the previous step.

5. Click Upload. The test overview opens:

   

   Note

   If the script contains unsupported plugins, then the script is not imported. For more information, see Supported plugins and elements of JMX scripts.

6. Review the imported files, thread groups, and load profile. If necessary, to replace the JMX script and supporting files, click Re-upload.

7. Optional: Edit a load profile.

8. Optional: Configure the profile graph display. Follow these steps:

   • To merge the graphs of several steps, click the Merge steps toggle. The toggle becomes available when there are several steps in the thread group.

   • Select the testing time that you want to consider in detail on the graph.

9. Optional: Add SLAs.

10. Optional: Link a settings set.

Edit a load profile

1. In the Load profile area, click Edit. The page opens:

   

2. Optional: Configure the profile graph display. Follow these steps:

   • To merge the graphs of several steps, click the Merge steps toggle. The toggle becomes available when there are several steps in the thread group.

   • Select the testing time that you want to consider in detail on the graph.

3. Disable the thread groups you don’t want to use in the test.

4. For thread groups of the jp@gc - Ultimate Thread Group type, edit the load profile for each step:

   

   • Start delay (min). Delay before starting testing. Specified in minutes.

   • Duration (min). Test duration at maximum load with all VUsers running. Specified in minutes.

   • Ramp-up time (min). Time allocated to start all VUsers. If set to 0, all VUsers will start simultaneously. Specified in minutes.

   • Number of VUsers. The number of load threads. The intensity of the load depends on the number of virtual users, timers, and response time of the testing system.

   • Ramp-down time (min). Time allocated to stop all VUsers. If set to 0, all VUsers will stop simultaneously. Specified in minutes.

5. Add the required number of steps to the tread group and customize the load profile for each step as you did in the previous step of the guide.

6. Click Go back to test overview.

Add SLA

1. In the SLA area, click Add.

2. Go to the required tab.

3. Click + Add SLA, and configure the metrics:

   • Test

     

     1. Select one of the metrics for the test:

        • Average response time. Average system response time to a request or transaction.

        • Error rate. Errors are calculated only when executing all requests, excluding transactions.

        • Percentile 95. The value which is greater than 95% of response time for the test.

        • Request per second. Number of requests sent per second.

     2. Select one of the conditions: <= or >.

     3. Enter a threshold of the metric (SLA).

     4. Optional: In the fields Start and End, enter the period for which PFLB Platform calculates the metric at the end of the test.

   • Transaction

     

     1. Select the transaction and use case.

     2. Select one of the metrics:

        • Average response time. Average system response time to transaction.

        • Error rate. Errors are calculated only when executing a transaction, excluding requests.

        • Percentile 95. The value which is greater than 95% of response time for the transaction.

        • Request per second. Number of requests sent per second.

     3. Select one of the conditions: <= or >.

     4. Enter a threshold of the metric (SLA).

     5. Optional: In the fields Start and End, enter the period for which PFLB Platform calculates the metric at the end of the test.

   • Request

     

     1. Select the request, transaction, and use case of the test.

     2. Select one of the metrics:

        • Average response time. Average system response time to a request.

        • Error rate. Errors are calculated only when executing the request.

        • Percentile 95. The value which is greater than 95% of response time for the request.

        • Request per second. Number of requests sent per second.

     3. Select one of the conditions: <= or >.

     4. Enter a threshold of the metric (SLA).

     5. Optional: In the fields Start and End, enter the period for which PFLB Platform calculates the metric at the end of the test.

   • System metrics

     Note

     Before adding SLA with system metrics, follow these steps:

     1. Create a setting set with system metrics for the monitoring.

     2. Link the setting set to the test.

     

     To add an SLA with system metrics, follow these steps:

     1. Enter the host name of the testing system.

     2. Select one of the metrics:

        • Average cpu usage,

        • Average memory usage.

     3. Select one of the conditions: <= or >.

     4. Enter a threshold of the metric (SLA).

     5. Optional: In the fields Start and End, enter the period for which PFLB Platform calculates the metric at the end of the test.

4. Click Go back to test overview.

See also

• Configure SLA

• Example of getting SLA results using the API

Link a settings set

Settings sets allow you to run tests with different settings. You can reuse any settings set in new tests.

Note

For JMX tests, only the monitoring and webhook settings apply.

To link a settings set to a test, follow these steps:

1. In the Settings set area, click Link. The sidebar opens:

   

2. Select the settings set on which you want to link to the test.

3. Click Link.

For more information, see Add a settings set.

Run a test

Run the test immediately after creating it or later in the Tests page. For more information, see Run test.

To run the test, follow these steps:

1. Click Create test run. The sidebar opens:

   

2. Optional: Click Add label and enter the name of the label for the test. To display labels in the Test runs page, select the Copy labels from test checkbox. For more information, see Add labels to the test.

3. Optional: For Description, enter a test run comment. You will be able to see this information in the test run details, all test runs list, and trend reports, when selecting a specific test run.

4. In the drop-down list, select the region in which you run the test:

   • automatic. Automatic region selection.

   • AWS Asia Pacific (Mumbai);

   • AWS Asia Pacific (Tokyo);

   • AWS Europe (Frankfurt);

   • AWS Europe (Ireland);

   • AWS US East (N. Virginia);

   • AWS US West (N. California).

   Note

   Only the automatic and AWS US East (N. Virginia) values are available for free users.

5. Optional: To run a debugging test, click the Debug run toggle. For more information, see Run a debugging test.

6. Click Run test.

The test will run after some time.

PFLB platform speaks for itself

Run a test to see how the platform works in real life. It takes only 15 minutes for a trial test. It easy and you’re gonna love it.

Try for free