When to Request the Page

Sometimes when tests execute multiple iterations, it is desirable to request a page only once (in the beginning or at the end) to perform initial or final actions. For instance, in a test case, a user logs in, performs some actions, and logs out. During the test run, you want every VU to log in only on the first iteration and log out only on the last iteration, while other pages should be repeated multiple times.

You can also apply this to a transaction level to request a transaction at a certain point in the test.

Use the When to Request the Page property to configure such tests. Set this property to On 1-st Iteration on the login page and to On Last iteration on the logout page.

The table below shows how to use this property.

When to Request the Page	Properties
On All iterations	(Default) The page or transaction and all its requests will be sent in all VU's iterations.
On 1-st iteration	The page or transaction and all its requests will be sent only in the first iteration. This is used for a log-in type page.
On Last iteration	The page or transaction and all its requests will be sent only in the last iteration. This is used for a log-out type page.
Disabled	The page or transaction is disabled, and all its requests will not be sent.
Every-x-iterations	The page or transaction and all its requests will be issued on the first and every number of iterations after that, specified in the Number of iterations property.
Every-x-minutes	The page or transaction and all its requests will be issued on the first and at least every number of minutes after that, specified in the Number of minutes property.