I’m running a set of thread groups (consecutively) and I need to reset a number of parameters at the start of each thread group so that they have a unique value.
Presently I’m referencing a User Paramaters node using a test fragment, and setting the value to value-${__time()}. Unfortunately, this results in the value being used verbatim (without resolving the time).
Is there a better way to achieve per-thread group variables that include function calls?
Works fine for me (Jmeter 2.5.1), as per below example.
Sample params set to
${__time(HMS,)}andvalue-${__time()}successfully resolved, generated and updated (once per iteration) for each thread (in this case:3 Thread Groups, 5 threads @ 3 loops).Can you please answer why are you using User Parameters via Test Fragment (as per your post)?
…And several articles, just fyi:
Parametrization in JMeter with user parameter
JMeter Variables vs. Properties. vs. Parameters
UPDATED:
Please find below results for example with both User Params and test logic put into Test Fragment and called from Module Controllers.
Works the same way as in sample above: successfully resolved, preserved between samplers in separate loop and updated (once per iteration) between loops for each thread (well, I ‘ve commented in screen the rest of thread groups to get output for the first only; works fine with all TGs enabled too).
I think you could also try to put User Params config from Test Fragment to each thread group and leave in Test Fragment only test logic – if the above schema will still not work for you:
It’s not very nice but both the Module Controller and Include Controller are still quite “buggy” and sometimes unpredictable.
You could also try to debug problem controllers in your scenario: select controller > click Help in jmeter’s main menu > click Enable Debug > look into jmeter.log for details after execution.
You could also look onto custom Parameterized Controller – maybe it will work better.