Running schedules
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 with one user or a schedule 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. - Cloud schedule overview
Schedule provides a way to apply huge user load on the application under test. To apply that amount of load, you need good infrastructure support ranging from physical desktop computers with enough RAM, Processors, and different operating systems. You need labs to host the computers. There is good amount of investment required. You can cut down on that investment by running the schedule in a cloud location. - 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. - Controlling execution of reports from Eclipse viewer
When a schedule is in the running state, you can perform the following actions from the Eclipse viewer to cater to the need of the run. - Controlling execution of reports from web browser
When a schedule is in the running state, you can perform the following actions from the web browser to cater to the need of the run. - Controlling the test runs from web analytics report
When a schedule is in the running state, you can perform the following actions from the web analytics reports to cater to your need.
Feedback