0

I have a JMeter test plan where I’m using an Include Controller that references a Test Fragment.

The Thread Group is configured with a duration of 1 hour.

When running the script with the Include Controller, the execution keeps running for 7–8 hours, far beyond the configured 1-hour duration.

When running the same script without the Include Controller, the test completes within the expected 1 hour and achieves the targeted number of samples.

So my questions are:

Is it possible that using an Include Controller with a Test Fragment can cause the test duration to extend beyond the configured time?

Has anyone faced a similar issue, and if so, what was the workaround or best practice?

Any guidance would be appreciated.

Steps to reproduce the problem

  1. Create a script with any site.
  2. Add simple controller and save as test fragment.
  3. Now add include controller under thread group.
  4. configure the test fragment in the include controller.

JMeter Version 5.6.3 Java Version open jdk version 8 OS Version Microsoft windows

Improve this question

2 Answers 2

Reset to default
0

If you use Include Controller with a Test Fragment, JMeter may run longer since each inclusion loads and processes the fragment separately, increasing execution overhead and resource usage.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

Include Controller is designed to work with external JMX files.

If you want to re-use a part of a test plan (Test Fragment) in multiple locations of your .jmx script - go for Module Controller.

More information: Using JMeter Module Controller

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.