ThreadGroups stands for a user and the suite should be able to take care of that

[rschwietzke]

Problem

When replying a JMX script as XLT scenario, one has to take care of the ThreadGroup because this is a virtual user aka scenario. XLT cannot simply reply all thread groups, but one has to tell XLT which one to reply to map corretly thread groups aka virtual user to the XLT concept of a user and scenario.

Ideas

• When you want to run a particular one, you have to define its name as part of the XLT Java class.
• If you don't specify anything, all will be replayed in order, hence if you have one script per user scenario, things run nicely.

[Glenmorangie]

Currently the suite will replay everything it found. Multiple thread groups will be listed as actions, with the according requests listed.