Bug 52596

In the current JMeter (all the way up to 2.6), Thread Groups cannot be 'grouped' in any way in a test plan. Purely for organizational sake, it would be nice to be able to have some sort of 'folder' to group together Thread Groups.

Some features that would be desirable for the folders:

1) Disable entire folder (and all test elements within). (Priority High)

2) Hide/Show folder elements - collapse all sub-elements to a single line. (Priority High)

3) Independent Test Scope for 'Config Elements' within a folder - the ability to setup config elements that control the configuration of only thread groups (or sub-elements) within the folder. (Priority Medium)

4) Multiple layers - e.g., the ability to create folders within folders, for organizing various sets of test functionality. (Priority Low)

5) Include "test plan" as a folder. The ability to load a separate test plan as a folder in my current test plan. Ideally, it would load the currently saved version of the separate test plan when I load the 'master' test plan (similar to the Include Module), but it would actually suck the entire plan into the folder - and let me edit it there. (Nice to have)

Use Case:

I have a test plan that includes 10 thread groups. The first 5 thread groups perform a variety of data setup functions, which are necessary for the second group of 5 thread groups. It would be nice to group these into 2 folders: "data setup" and "main test". Moreover, there are times where I want to setup the data, but not run the "main test" thread groups immediately (I might have some review or additional 'non-automated' setup tasks that I want to run.) So it would be very handy to be able to disable 1 folder, and only run the other.

Lastly, It would be very nice to have different test scope for each folder - so that I can setup config elements within the folder to control the thread groups within that folder. Needless to say, if we had this, we would still need the ability to have a 'master' set of configs (peers to the first folder level) that would be the default config for all sub-elements, but within a folder you could override the defaults with local scope config elements.