Getting Started - JMeter
Follow this guide for a basic example of running a JMeter test plan. For our example we will use a really simple test plan which simply makes an HTTP GET request for http://sample.testable.io/stocks/IBM. The test plan can be found here.
Start by signing up and creating a new test case using the New Test Case button on the dashboard or Test Case -> New... in the left side panel.
Enter the test case name and then press Next.
Select JMeter Test Plan as the Scenario type.
Click the Add Files button to upload the Test Plan (.jmx) file. For more complex tests you can upload any test related file here (e.g. CSV data, plugin jars, jmeter properties file, etc).
Click the Smoke Test button in the upper right to run your test plan with 1 thread and 1 iteration on a Testable test runner. The output of the run will show up in the Smoke Test Output once it finishes.
And that's it, we've now defined our scenario! Click on the Configuration tab or press the Next button at the bottom to move to the next step.
Now that we have the scenario for our test case we need to define a few parameters before we can execute our test:
- Load Profile: Select Flat to ramp up to a constant number of concurrent users for the test.
- JMeter Instances Per Region: Number of JMeter instances that will execute your JMeter test plan in parallel in each region selected.
- Test Runners: Choose the test runners from which to run this test (e.g. on our public shared grid). Each test runner region will execute the number of JMeter instances defined above.
- Type: Select Iterations to have each concurrent client execute the entire JMeter test plan sequentially a set number of times regardless of how long it takes. Note that the JMeter thread group can specify multiple iterations too which will be honored. Choose Duration if you want each client to continue executing the test plan for a set amount of time (in minutes).
And that's it! Press Start Test and watch the results start to flow in. See the new configuration guide for full details of all configuration options.
For the sake of this example, let's use the following parameters:
Once the test starts executing, Testable will distribute the work out to the selected test runners (e.g. Public Shared Grid in
AWS N. Virginia).
In each region, the Testable runners execute 5 JMeter instances 1 time through. Our example test plan will call HTTP GET http://sample.testable.io/stocks/IBM on 5 threads, 5 iterations each. This means that in total we should get 125 results (5 Testable JMeter instances * 1 Testable iteration * 5 JMeter threads * 5 JMeter iterations = 250).
You can see various graphs, metrics, and grids in the results. If you click on any resource in the results grid, the charts below will update to be specific to that resource only.
Check out the JMeter guide for more details on running your JMeter tests on the Testable platform.
We also offer integration (Settings -> Integration) with third party tools like New Relic. If you enable integration you can do more in depth analytics on your results there as well.
That's it! Go ahead and try these same steps with your favorite website or API and feel free to contact us with any questions.