This article describes the Environments page. This page allows you to see all the different execution environmentsThe execution environment is defined by the browser, operating system and viewport size when the test was started. These values, along with the application name, test name and branch name determine the baseline that will be used in a run. under which visual UI tests were run by your team. This page also provides a way to assign a name to a specific environment and to rename or delete existing names.
Once you have named an execution environment, you can use the SDK to specify that a test should run against a baseline that matches the environment of that name. See Run test against a baseline that matches an environment name for more information as to how to do this.
You navigate to the Environments page using the page navigator. The page consists of a summary panel, a toolbar, and a table of all the execution environments and their names.
The summary panel displays the total number of environments, the number of different browser types and operating systems, and the number of viewport size variations.
The toolbar provides the standard row selection, row delete, page refresh and filter controls. See Test manager UI overview for more details.
The main part of the window consists of a table with a row for every combination of browser type, operating system and viewport size under which a test was run. There are columns for the Browser, OS and Viewport, and a column for the Name that is assigned to that variation. The Name column will be empty if a name is not currently assigned to that environment.
You can organize the contents of the table as follows:
The fact that a row is displayed does not mean that the system currently includes test results or baselines with that environment. If you want to know if a test result or baseline with this environment exists, then you can use the filtering options on the Test results and Branch baselines pages respectively.