Running a Load Session
After configuring a Load Session, you can run your Load Session. This chapter describes the procedure for running your Load Session, and the way WebLOAD Console behaves while a Load Session is in progress.
WebLOAD Console collects a complete set of test data while a Load Session is running. You can configure reports that include only the data needed. Reports can be configured during or after a test.
WebLOAD Console run commands can start, pause, and stop your Load Session while it is in progress. These commands are detailed in this chapter.
Starting a Load Session
You can start a Load Session in one of the following ways:
- Click the Start Session icon in the Quick Access toolbar.
- Click Start Session in the Session tab of the ribbon.
- From the WebLOAD Wizard - Finish dialog box, select the checkbox to run the Load Session immediately and click Finish.
- From the Goal-Oriented Test - Finish dialog box, select the checkbox to run the Load Session immediately and click Finish.
Running a Load Session from the System Memory
You can run a test from the configuration parameters in your system memory, without saving the Load Session. If you start running a Load Session without saving the Load Session configuration, you are prompted to save the Load Template.
The following message box appears.
Saving the Current Load Template
To save the current Load Template:
- Click Yes.
The test session definition is saved to a Load Template (*.tpl) file.
Launching WebLOAD Console through the Command Line Interface
You can perform load testing through a command line interface. You can enter the WebLOAD Console launch command into a batch file or into an external script and WebLOAD Console will run directly, without user intervention, using the parameters specified.
Note: You can also perform unattended WebLOAD Console testing at prescribed times by running WebLOAD in Jenkins . Jenkins CI is a Continuous Integration server that is used by Agile development teams to run their builds, tests and deployments as well as their performance tests if possible. Jenkins is extendable by means of plugins. As of WebLOAD 10.1, a WebLOAD plugin is available for Jenkins. For more information, refer to the WebLOAD Automation User Guide
To run WebLOAD Console through the command line interface:
Enter the WebLOAD.exe command together with a series of optional parameters (described below) into your external script to automatically launch a WebLOAD test. When your script runs, the executable file will invoke WebLOAD Console and run the specified test according to the specified parameters.
Note: Verify that the script used with the template specified, and any included files, are accessible to the Load Template or Load Session file that will be run.
Syntax
Use the following syntax to define the parameters for running a WebLOAD test through a command line interface:
WebLOAD.exe [<file name to open>] [<file name to save>] [<flags>] [<time>] [/ag <script name>]
Parameters
When running a test invoked by the executable, you can specify the following parameters:
| Parameter | Description | Comments |
|---|---|---|
| File name to open | The name of the *.tpl or *.ls file (Load Template or Load Session file) to run. |
Optional parameter |
| File name to save | The name of the *.ls file containing the test data. This file will be saved in the current directory unless otherwise specified. |
Optional parameter |
| Flags | - /ar – Automatically run the WebLOAD test without waiting for user input. If this flag is not specified, the Console is called up with the specified Load Template/Load Session but the test is not automatically run. The system waits for user input. - /ar - /vc – The number of Virtual Client licenses to allocate when using WebRM License Server. - /pc – The number of Probing Client licenses to allocate when using WebRM License Server. - /rc |
Optional parameter |
| /ag
|