You can configure the run-time system environment in which your tests run using the usual methods (see
Run-Time System Configuration), but those settings will remain in place for each subsequent set of tests run until the values are changed. A more efficient method is to configure an environment that is automatically applied when you initiate a particular test run. You can do this by creating an application configuration file
or Java properties file
containing the usual run-time system configurations. The naming of this file depends on the type of tests that are in your test run:
- Native COBOL tests
- The application configuration file must have the same base name as the base name of your test suite (i.e. the base name of your
.dll,
.int,
.gnt,
.so, or
.mfu file), and an extension of
.mfgcf. Place this file in the same location as your test suite and it will be used during the test run.
- Use your IDE to create the application configuration file.
The
.mfgcf file can be generated by creating a unit test project and fixture file, setting the environment variables and switches in the run-time configuration for the project, and then running the standard test case that was created with the fixture file: during this test run, the
.mfgcf file is created in the output folder, where you can copy and rename it for use on the command line.
- JVM Procedural COBOL tests
- The Java properties file must have the same base name as the base name of your test suite (i.e. the base name of your
.jar,
.so, or
.mfu file), and an extension of
.envprops. Place this file in the same location as your test suite and it will be used during the test run. Create the plain-text file with any text editor, placing each setting/value pairing on a separate line.
