GGC 4.00 new features

A summary of new features and changes in functionality introduced with Genero Ghost Client 4.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 4.00 upgrade guide.

Previous new features page: GGC 2.00 new features.

Table 1. What's new in GGC 4.00
Overview Reference
The Genero BDL API provides functions to return all or part of the AUI tree. See AUI tree information.
To perform stress tests, you can run multiple instances of the GGC using the --instance-count and --instance-delay options of the ggcadmin tool. See ggcadmin.
You can provide user data using the command line or a file. You can set this data for a test scenario using the ggcadmin or fglrun tool, and fetch this data into your test scenario using the getUserData() function. See:
The Genero BDL API has been enhanced to support multiple calls to registerFrontCallHandler(). Previously, this was possible with the Java API only. See registerFrontCallHandler().

You can retrieve the scenario ID.

See getScenarioId().
When recording an application log file, you can capture the application state at any given point by taking a snapshot. Afterward, the ggcgen --check-on-snapshot option can insert code from the check templates into the test scenario. You can also load the Genero AUI tree at the time the snapshot was taken into your test scenario. See Working with snapshots.
You can implement your own testing framework and not have the GGC manage the execution of the scenarios with client.disableScenarioWrapper(). See How to implement your own testing framework.
You can programatically speed up or slow down the pace of the execution of your test scenario with the setSpeedRatio method, found in both the Genero BDL API and the Java API. For the Genero BDL API, see setSpeedRatio().
For tests written using the Java API, you can change the log configuration for a session at runtime with the LoggerConfig() class, to modify the log configuration that had initially be set for the GGC in the ~/.ggc/log.properties file. See Set logging options at runtime (Java API).