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 local schedule or test
You can run a test locally or a schedule, in this context, is used to refer to VU Schedule and Rate Schedule on remote locations with a default launch configuration.
Running a long run mode SAP GUI test
When running a SAP GUI test that could last for many hours and could use up the operating system resources, you can choose to run the test with the Long Run Mode process. It is an external process that restarts automatically after the specified number of SAP sessions are over. So, tests of longer duration tests are more likely to finish.
Running long duration Citrix tests
When tests exceed many hours, resource consumption issues can cause problems for the Citrix clients. The long run mode increases the reliability of long duration tests with the Citrix protocol by running the test using multiple processes.
Testing with Docker images IBM® DevOps Test Performance (Test Performance), IBM® DevOps Test UI (Test UI), and Test Performance Agent are available for download as Docker images. You can use them to fulfill the continuous testing aspects of your DevOps lifecycle.
Testing with IBM Cloud Private
You can automate your testing environment by using Docker container images of the workbench and agents on top of IBM® Cloud Private.
Adjusting delays in HTTP tests
You can configure HTTP tests to use client-side processing delays. Client-side processing delays wait for the first character or last character that is received in a response for a previous request in order to better emulate the work done on the client computer. You can also scale the recorded delays in HTTP tests to change the rate at which a test runs.
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.
Controlling cache sizes
If you use an infinite loop and the number of cached responses in a test increases exponentially, you can set a limit to cache for a user group in the schedule.
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.
Debugging HTTP tests
If a test does not behave as expected during playback, you can use the protocol data and test log to assist in debugging the test.
Debugging Citrix tests
The Citrix dashboard is an optional panel that displays detailed information and control commands for each virtual user during the run of a schedule. This is useful for debugging your tests and allows you to pause, interact, resume, or stop the execution of individual virtual user sessions.