GGC 2.00 new features
A summary of new features and changes in functionality introduced with Genero Ghost Client 2.00.
Important:
This page covers only those new features introduced with the Genero GGC version specified in the page title. Check prior new features pages if you migrate from an earlier version. Make sure to also read the upgrade guide corresponding to this Genero version.
Corresponding upgrade guide: GGC 2.00 upgrade guide.
Previous new features page: GGC 1.10 new features.
Overview | Reference |
---|---|
GGC is now a centralized backend to provide better load testing. | See The Genero Ghost Client framework. |
A method is provided for multi-row selection. | See setRowSelection() |
Methods are provided to retrieve column values in a matrix, table, tree, or screen record in your test scenarios and to return values for a column at a specified row. | See getColumnValue() and getColumnValues() |
Network load is simulated by loading all images attached to the AUI Tree. ( Not done in TCP / Direct mode, only via GAS) | No additional reference. |
The GGC is embedded in the FGLGWS package in the $FGLDIR/testing_utilities/ggc directory. | See Install and configure for Genero Ghost Client |
Documentation about the APIs that make up the GGC framework can be accessed:
|
No additional reference. |
Templates with snippets of generic code for testing are available in the installation
directory. They are located in GGCDIR/template . |
See Templates |
A feature of templates allows you to create a skeleton scenario with code from the header and footer templates. This provides the code that forms the basis of the test application. | See |
Overview | Reference |
---|---|
The ggcadmin is an administration tool providing commands to start and stop the BDL scenario server, and to run Java scenarios in either direct or UA mode. | See ggcadmin |
The ggcgen is the tool that you use to generate test scenarios. There are commands to generate BDL and Java scenarios. | See ggcgen |
The logging mechanism for the Genero Ghost Client allows you to control the level of logs and the output messages. | See log.properties. |
To ease Single Sign on detection, an HTTP handler named
GIPSSOHandler is available. |
See GIPSSOHandler. |
Support for front calls is available. | See Front calls and Default front calls. |
GGC tools (ggcadmin,ggcgen and BDL scenarios) can load command options from a default argument file. | See Default argument file. |
Overview | Reference |
---|---|
There is a debugging tool that is activated by the "--dump_* "
options of the ggcgen tool. |
See ggcgen |
The ggcgen
--no-wait option allows for the generation of test scenarios without instructions
for delays between actions. |
See ggcgen and Test speed ratio |
The --check-messages option of the ggcgen
tool generates code that tests MESSAGE and ERROR messages.
Templates are provided for these checks. |
See ggcgen. |
Overview | Reference |
---|---|
The --environment-file option of the
ggcadmin tool (Java) and the GGC scenario program (BDL) allows environment
variables to be provide in a file for the environment of the DVM that is started by the
scenario. |
See ggcadmin or fglrun and the Genero BDL test scenario and Set test environment. |
The --fename client-name option of the
ggcadmin tool (Java) and the GGC scenario program (BDL) allows you to specify an
alternate default client name. |
See ggcadmin or fglrun and the Genero BDL test scenario. |
Starting at 2.00.08 | |
The --check-as-failure option of the
ggcadmin tool (Java) and the GGC scenario program (BDL) allows you to treat failed checks as a
scenario failure. |
See Scenario failures and check failures, ggcadmin or fglrun and the Genero BDL test scenario. |
Starting at 2.00.16 | |
The --dvm-available option of the ggcadmin
tcp tool (Java) and the GGC scenario program (BDL) direct TCP mode allows you to specify the delay (seconds)
for the DVM to start and be available. |
See ggcadmin or fglrun and the Genero BDL test scenario. |