Multiple Applications Support
To support multiple applications with the same AtcgGeneratorSchema schema, some options are passed in using app.atcgGetControlOptions method in the AtcgTestCodeSchema schema. This includes:
-
Generated schema name
-
Generated superschema name
-
Generated superclass name
-
Name of the logMessage method of the driver schema
-
List of schemas to be tracked
-
List of noise methods to exclude from method tracking
The global.atcgMyControl method in the GAtcgGeneratorSchema class can be accessed from the atcgGetControlOptions method, so you can actually set other options that are not provided for with explicit parameters.
Instead of having an AtcgTestCodeSchema for each application, you can also test multiple applications out of a single AtcgTestCodeSchema. In the Erewhon version of AtcgTestCodeSchema, the startup method of the EDIProfile class decides which application to emulate by getting the application name from the [ATCG] section of the Jade initialization file. The startup method is called by AtcgRecordApp and AtcgReplayApp. The two demonstration classes set the application name in their startup methods, so you do not have to set it externally when replaying profiles. AtcgRecordApp will bring up the application specified in the [ATCG] section of the Jade initialization file at the time, for example:
[ATCG]
TestApp=Administration
This is an example in the Erewhon schemas only; it is not supported by default in the generic schemas as there are no user applications in the generic schemas.
