JMeter has been one of the more popular, open-source load and functional testing tools in the market. However, due to its complex nature and limitations, such as only simulating protocol-level traffic, it can prove troublesome when running load tests for web applications or SPAs (Single-page Applications). Since JMeter is not a browser, it requires additional significant knowledge and setup time to be able to properly and adequately simulate performance from the end user’s perspective. This article sets out how to convert from JMeter to LoadView tests.

Additionally, unlike LoadView, where you can quickly select from multiple load injectors from around the world, JMeter load is generated from your local machine or servers, which leads to unrealistic real-world conditions. Not only that, setting up your own load generators is time-consuming and expensive.

To convert an Apache JMeter web application load test into a LoadView load test, you can easily transfer data manually in a few basic steps outlined below in this article.

JMeter into LoadView: Configuring a LoadView Task

Before you begin, you will need to have a LoadView account. You can get started with LoadView for free by signing up here. If you have a LoadView account, you will need to log in to your account. To transmit data manually, follow these next steps:

1. First, within the Apache JMeter application, open the JMX file with the script you are looking to convert.

2. Create a new LoadView Load Test and choose HTTP(S) Task.

3. Copy the request data from JMeter fields to the corresponding fields of the LoadView HTTP(S) task. For example, copy the target URL to the URL field, set up HTTP method in the Request Type field, and add headers in the Headers section, copying their names and values.

jmeter into loadview4. Configure the task settings as described in Configuring HTTP(S) Task and save the LoadView device.

5. If you have more than one request to the same web application within JMeter script, add new tasks to the current device and copy the corresponding JMeter data for each request as described. Due to the global headers in JMeter, you’ll need to copy the headers from the JMeter HTTP Header Manager to each task of the LoadView device.

Configuring a LoadView Test Scenario

Once the HTTP parameters of the test have been configured in LoadView, the LoadView test execution scenario must be set up. Use the Thread Properties of JMeter Thread Group to specify the corresponding Load Type parameters of the LoadView Test Scenario.

Configuring Threads and Ramp-up Period

The ramp-up time is a very important part of the load testing process, but often goes overlooked. If you are planning to test with a large number of concurrent users, you don’t want to immediately ramp-up your test to the maximum number of concurrent users as it doesn’t reflect real-world conditions and it may have unintended consequences, like unintentionally crashing your site. If that happens, you won’t know what your site can handle or responds before that point. By setting a ramp-up time, you can gain a more accurate representation of how your site or application handles concurrent traffic at different levels.

For more information about properly determining concurrent users for load tests, visit our Analytics to Concurrent Users Calculator & Formula Knowledge Base article.

To specify Number of Threads and Ramp-up Period, use the Raise By scenario step in LoadView:

1. First, calculate the ramp-up period in minutes:

Ramp-up Period in minutes = Ramp-up Period / 60

Next, calculate the number of threads that need to be up per minute:

Number of Threads per minuteNumber of Threads / Ramp-up Period in minutes

For example, if there are 30 threads and a ramp-up period is 120 seconds in JMeter, it will take LoadView two minutes to get 30 concurrent users up. The number of users to raise by per minute is 15 (30/2).

2. Specify the Ramp-up Period in minutes and Number of Threads per minute in the corresponding fields of the Raise By step.

Setting up Test Duration

If you need to repeat the same test configuration more than once (Loop Count is not set to 1, or Duration is set in JMeter), add the Hold For step to the LoadView Load Test Scenario and specify the time in minutes to hold the load.

By default, load test duration is limited to 40 minutes in LoadView. If you need to run the test longer then 40 minutes, please contact technical support to activate a load test time extension.

Setting Ramp-down Time

Similarly, ramp-down time is another factor that needs to be considered during load testing. Ramp-down time would correlate to the traffic you would see at the end of your peak hours, where you would normally tend to see a drop in the number of concurrent users. For this, you would want to set a similar strategy for load testing best results. Learn more about setting up a Load Curve load test.

If Loop Count is set to N loops, the test duration is calculated based on the test iteration duration (task duration):

Test Duration = Loop Count × iteration duration

The LoadView test iteration duration can be found on the Waterfall Chart.

To run a stress test at a specific time, use the Start Test Later option. For more information, see Concurrent Load Test Execution.

If you need any further assistance with converting JMeter load tests into the LoadView platform, please contact our technical support team. Our team is available 24/7 to assist with all your load and performance testing needs.

Or if you already have a LoadView account, you can submit a ticket from directly within the LoadView platform. To submit a support ticket, simply log in to your account. From the top right-hand side, hover over Support, then select Tickets to submit a request.