After
you have added the user groups, tests, and other items to a schedule, and
you are satisfied that it represents a realistic workload, you run the schedule.
Running a schedule or test
You can run a test locally
with one user or a schedule with a default launch configuration.
Setting a launch configuration
Instead of using the default
launch configuration, you can specify the file name for the execution
results, the name of the folder for the execution results, and, for
a test, the number of users.
Running a configured schedule
If you do not use the default
launch configuration, you can configure the schedule and then run
it.
Configuring multiple host names for a location
You can run several
locations on the same computer by configuring multiple host names
for a location. This configuration affects all tests running at that
location; all tests will run with the configured port.
Automating tests
You can run a schedule from the command line. You can also set
preferences to export results after the run completes from the command line
or from the workbench. Together, these features let you run tests and analyze
results without opening the workbench. You can even write scripts to process
the exported results.
Increasing memory allocation
The virtual users that access
your Web server require memory to prepare requests, send requests,
and receive responses. Because the amount of memory is not automatically
set on remote computers, you might receive an out-of-memory error.
To correct this situation, increase the memory allocation for that
computer.
Changing the number of virtual users during a run
If the number of virtual
users initially defined is incorrect, you can change the number of
users. The change can be applied to one stage or to all remaining
stages in the schedule.
Changing the problem determination level during a run
You can change the level
of problem determination logging during a run. By default, only warnings
and severe errors are logged. Typically, you change this level only
when requested to do so by IBM® Software Support.
Interrupting a run
You can stop a run before it is completed. For example,
you might detect serious problems in the run and not want to wait
for it to finish. You can optionally save the results and the test
log, which enable you to run reports on the run.