Share via

How do I split up a large JMeter test into multiple smaller ones and have them all run

Stefan Schweigert 20 Reputation points
2025-11-05T19:30:20.49+00:00

Hi there,

I have a large JMeter test script (200 mb) and I would like to be able to run this test through Azure Load Testing.

I am able to split the tests into multiple files, each one with one or two Thread Groups.
How do I reference the other tests from my 'main test' as configured in the test run?
I have tried the following but no luck.:

  1. Uploading a single zip file containing the entire JMeter script, but I cannot select the file as the 'main'.
  2. Breaking apart the groups into different files, then adding a Test Fragment to the main test plan and using Include Controllers to reference all the other files.

I couldn't find any specific instructions on how to deal with this scenarios; any suggestions would be greatly appreciated!

Thanks, Stefan

Azure Load Testing
Azure Load Testing
An Azure service that enables developers and testers to generate insights on how to improve the performance, scalability, and capacity usage of their application
0 comments
Answer accepted by question author
  1. Natheem Yousuf 340 Reputation points
    2025-11-13T05:31:21.77+00:00

    here’s a practical way to handle it.

    1. Preferred: upload one ZIP with a single “main” .jmx and all referenced files (put the other .jmx fragments, CSVs, etc. in the same folder and use only filenames, not full paths in your Include Controllers). When you create the test, pick the main .jmx as the entry file. Azure Load Testing will copy all uploaded files to the test engines. Microsoft Learn
    2. If Include Controller still fails (some users/reporting show Include Controller isn’t reliably supported), convert your fragments into Test Fragments inside the same .jmx and call them with a Module Controller — or merge the smaller .jmx files into one main .jmx before upload. There’s an open issue/feedback on this limitation. GitHub

    Alternative: keep each thread-group file as a separate test and run them sequentially or in parallel from CI/CD using the Load Testing YAML / CLI (az load test) and then stitch/compare results yourself. The YAML approach works well when a single big JMX is impractical.

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.