Test Case Groups

Toolbar

Button	Action
	Create a Test Case Group
	Edit the selected Test Case Group
	Delete the Test Case(s) from the Test Case Group
	Verify test case group…

Help Box

Test Case Group

When at least one Test Case Group is created,
Sequential-Concurrent TC mixing model is used:

- Test cases in a TC Group are executed sequentially.

- Multiple TC Groups are executed concurrently.

- VUs are distributed between the TC Groups
proportionate to their Mix Weight properties.

- Only test cases included in TC Group(s) are executed.

To go back to the Concurrent TC mixing model,
delete all TC Groups.

See Also:
Sequential Test Case Groups

Test Case Groups Dialog Commands

Button	Action
	Add Test Case(s) to the Test Case Group
	Delete Test Case(s) from the Test Case Group
	Move Test Case Up for earlier execution
	Move Test Case Down for later execution

Test Case Group Properties

Property	Description
Name	The Test Case Group name
Description	The Test Case Group description
Disabled?	Set to Yes to exclude the test case group from the test run. Its mix weight will be set to 0.
Mix Weight	The relative frequency (in units) of the Test Case Group replays in the mix. Every VU is assigned to a specific Test Case Group selected in a round-robin order while skipping some of them to achieve the VU distribution corresponding to the mix weights.
User Group	If user groups are assigned in the server authentication grid, select the user group that will execute this test case group. Leave blank to have VUs not assign to any user group execute this test case group.
Cache-Control	Select "Enabled" to emulate browser caching and session management. Select "Disabled" to emulate browsers with disabled caching (all requests will be sent) and restarting browsers before starting a new iteration (browser sessions will not persist across test iterations).
New VU %	Percentage of the New vs. Returning VUs. Note: (a).On the 1-st iteration, new VUs will have an empty cache, just as a first time user. All requests will be sent. (b).On the 1-st iteration, returned VUs will have a primed cache. Caching rules for each request will be determined based on server caching headers. (c). On the subsequent iterations, all VUs are treated as returned VUs.
Maximum Iterations	The maximum number of iterations this test case can be executed per VU.
Agent name	The agent designated for the execution of this test case group. Leave blank to run it on all agents.
Action on error or timeout	After an error or timeout is encountered: to continue the current iteration, select: "Continue"; to abort the current iteration and proceed to the next one, select "Abort Iteration"; to stop this VU, choose "Abort VU".