You can start Silk Performer load tests directly from a command-line interface. This is especially useful when you create a batch file, which executes a number of load tests consecutively.
To start Silk Performer from a command line, use the following syntax:
performer [project file [/Automation [refresh rate] [/WL:workloadname] [/StartMonitor]] [/Resultsdir:directory]]
Here is a sample command with sample parameters:
performer "<my documents>\Silk Performer <version>\Projects\AllDayWorkload\AllDayWorkload.ltp" /Automation 5 /WL:AllDayWorkload10
Parameter | Description |
---|---|
project file | Name of the project file that defines the load test to be executed. |
/Automation | Automatically starts the load test that the specified project file defines. If you omit this parameter, Silk Performer opens the specified project. |
refresh rate | Refresh rate, in seconds, at which the Monitor window refreshes. If you omit this parameter, then no refresh occurs. |
/WL:workloadname | Name of the workload in the specified project file. If you specify a workload, it is set as the active workload in the project file. |
/StartMonitor | Starts Performance Explorer’s monitoring facility when running the test. |
/SOA | Launches the Silk Performer SOA Workbench. |
/Vision | Specifies to start as Silk Performer Monitor Workbench. |
/eCatt | Specifies to start as Silk Performer SAPGUI eCatt Workbench. |
/Abort | Aborts running tests. |
/? or -? | Displays help about the Silk Performer command-line interface. |
/Resultsdir:directory | Specifies the directory where the load test results are stored. The directory path can be absolute or relative to the project file. |
/ImportStAsset:asset file?project name | Imports Silk Test assets to Silk Performer. Asset file is the absolute path to the asset. Project name is the name for the new project. This value is optional. When omitted, the default project name is used. |