Rate Runner group overview

With the Rate Runner group, you can group tests in a logical order and run them in parallel.
You can control test execution in Rate Runner groups in several ways:
  • Group tests by characteristics: For example, you could have two groups such as Buyers group and Browsers group. These groups represent the types of users on your system.
  • Influence the order in which tests are run: When you run the Rate Schedule, the first test in each group runs in parallel, and not in sequence. After the first test in the group is completed, the second test runs, then the third, and so on.
The following Rate Schedule contains one user group.

Schedule with a group called Browsers and Buyers. The group contains five tests: Open, Browse, Open, Browse, Bid.

If you run this Rate Schedule with 10 iterations, they are assigned to the only Rate Runner group: Browsers and Buyers. When the run starts, the 10 iterations start running the first test in parallel. As soon as one test is finished, an iteration moves to the second test. Thus, you have 10 iterations, all starting simultaneously and running each test sequentially. This does not give you much control over the run.

The following Rate Schedule contains the same tests in the same order, but they are divided between two Rate Runner groups. Conceptually, this Rate Schedule is easier to understand, because the user's tasks are grouped logically as Browsers browse and Buyers browse and then bid on a product.

Schedule with two groups. Browsers group contains two tests: Open and Browse. Buyers group contains three tests:  Open, Browse, Bid.