Working with Multiple Configurations

In some testing situations it is useful to use separate configuration files to switch between different configurations for different test runs. For example, if you routinely test your product under different versions of the JVM amchine, you could specify a different Java launcher command in each configuration.

Prior to running tests, use the Configure menu to load the required configuration file. See Loading an Existing Configuration for detailed information. These configuration files can be loaded from a central resource provided by your test group. See your test group for the name and location of the configuration files.

If your group does not provide an existing set of configuration files, you can create them by using the Configuration Editor to edit an existing configuration and then save each variation to a file name of your choosing. See Editing the Current Configuration for detailed information.

You can save these configuration files anywhere in your file system. Generally, however, the work directory should not be used to save configuration files. Clearing the work directory would delete the configuration file.

After these configuration files have been created, they can be used by any JavaTest harness in your test group to run tests.