Test environments

You can define custom environments to manage sets of variables such as application URLs and user credentials, and to configure profile overrides. When you run a test, the variables and override rules defined in the environment dynamically replace the values within your test script. You can easily change testing targets without modifying your test script by using environments because the environment-level configurations take precedence over the default values defined in the script.

You can create, edit, copy, move, and delete the environments. When you create an environment, a .dte.yaml file is created and listed under the Environments folder for the selected application in the test navigator panel.

Environments that you defined for an application are available for selection in the ENVIRONMENT tab of the Execute test asset dialog when you initiate a test run.

Profile overrides

In addition to managing variables, you can use environments to configure profile overrides. By using profile overrides, you can substitute a default profile, such as a specific browser or emulated device, with a different target profile, such as a cloud-native device or alternative browser, when you run tests.

In the Execute test asset dialog, you can either specify an Environment that carries override rules or select a browser or device profile in the Browser field. If you specify values in both the Environment and Browser fields, then the value in the Browser field takes priority.