Skip to end of metadata
Go to start of metadata

During a load test, StresStimulus will assign a test object to every new VU. The test object's mix-weight defines how many VUs will execute it. The test object's tier setting defines the order when the VUs will execute it. VUs for the next tier will not start until all VUs for the previous tier have started. Having test objects in different tiers can emulate an unexpected load at peak periods.

Tier setting

To set the tier setting of a test object, set the Tier property.

If at least one test object has a non-zero tier setting then the Tier column will appear in the VU distribution by Agent - TC dialog.

Mapping VUs to test objects

Consider the following test objects and their corresponding mix weights.

Test Object

Mix Weight

Browse Store6
Purchase Item4

The following table shows the difference in how 10 VUs are mapped to test objects for different tier settings:

Tier settings are the same

Test Object

Tier
Browse Store0
Purchase Item0

VU

Test Object

VUTest Object
1Browse Store6Purchase Item
2Purchase Item7Browse Store
3Browse Store8Purchase Item
4Purchase Item9Browse Store
5Browse Store10Browse Store

Tier settings are the different (lower-tier objects execute first)

Test Object

Tier
Browse Store1
Purchase Item2

VU

Test Object

VUTest Object
1Browse Store6Browse Store
2Browse Store7Purchase Item
3Browse Store8Purchase Item
4Browse Store9Purchase Item
5Browse Store10Purchase Item

Distributed testing

If running a distributed test then tier settings are honored within each load agent independently. For example, on load agent 1, if all VUs with Tier 1 test cases have launched, then VUs with Tier 2 test cases will begin launching, even if not all VUs with Tier 1 have launched on load agent 2.

  • No labels