fglrun and the Genero BDL test scenario
A generated GGC scenario implements a set of command line options.
By default, a GGC scenario program generated by ggcgen implements a set of options to control the testing parameters.
fglrun ggc-scenario-program {
ua |
tcp }
--help
fglrun price_sample.42m ua --help
ua
) and in direct mode (tcp
). Option | Description |
---|---|
-h
or
|
Displays help for the ua and tcp commands. |
--dump-command |
Expand the command line options that are loaded from a default argument file. See Default argument file. |
--fename client-name |
Specify the client name used by the GGC. Use this option to have the
GGC return a client name other than the default when running a test. By default, the GGC returns:
The client name is used when connection strings are exchanged, to identify the client type.
This is the value returned by |
-f argument or
|
Forward GUI to the specified
FGLSERVER. The AUI tree received from the DVM can be forwarded to a running GDC with
--forward-gui localhost:0 to provide a visual feedback of the scenario execution.
|
-F argument
or
|
Provides front call handler support for user- provided front call handlers. |
-p argument or
|
Specifies the port on which the server listens for connections (default is 6500) |
--check-as-failure |
Treat failed checks as failure. If any check fails,
the test scenario fails. The default is FALSE . |
-s argument or
|
Specify an execution speed for the test. The scenario generator injects wait delays. This parameter provides a way to run your tests faster or slower. For example, a ratio set to 1 equals 100%. This is the default or normal wait delay. A 10% increase in speed is achieved by setting the ratio to 0.1. For an even faster test, set the ratio to 0, which equals no wait delay. Setting the ratio to 2, increases the delay by a factor 2 (200% ), the scenario will take at least twice as long to execute. See Test speed ratio. |
--user-data
key=value |
Sets the value of a data
key. This option can be called multiple times to set multiple
name=value pairs. You then use the Genero BDL API method
|
--user-data-file filename |
Specifies the file
that contains user data. This file must contain a list of
name=value pairs, one per line. You then use the Genero BDL API method
|
Option | Description |
---|---|
-H argument
or
|
Provides HTTP handler support. For example, a default
HTTP handler (GIPSSOHandler ) is provided for Single
Sign on to authenticate a user with the Genero IDP SSO.
|
-u argument or
|
Specify the URL to start the application. For example, http://localhost:6394/ua/r/gwc-demo. |
Option | Description |
---|---|
-c argument or
|
Specify the runtime command
(fglrun). The argument is the program passed to the runtime to
test. Enclose the command and argument in quotations. For example, "fglrun price ".
|
-e argument or
|
Sets environment variables that will prepare the
correct environment to run the test scenario. The argument is a file listing the
environment variables in the
form: If environment
variables in values are to be expanded, they must be referenced (regardless of the platform) using
the dollar sign and curly braces, for example ${ENVIRONMENT_VARIABLE_NAME} . For
examples, see Set test environment. |
-w directory_name or
|
Specify the path to the directory containing the application being tested. The default is the current working directory. |
Refer to the Genero Business Development Language User Guide for details regarding the fglrun command.