Skip to content
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

Environments

An environment is a set of variable values for one place you test, such as Staging or Production. Steps refer to a variable by name, written as {env.<variable>}, and Copilot reads its value from the environment you choose when the steps run. The same test case can then run against Staging or Production without changing its steps.

Every environment starts with the project’s default variables. You override only the values that differ.

Environments are on the Environments tab of Test Assets.

Default variablesAn environment
HoldsOne value for every variableThe same variables, with some values overridden
Applies toEvery environment, unless it overrides the valueRuns that use this environment
Adding a variableAdds it to every environmentAdds it to every environment, with this environment’s own value
  1. In the left navigation, open Test Assets, then open the Environments tab.

  2. Click Default variables.

  3. Click Add Variable.

  4. Enter a Variable name and a Default value.

  5. To hide the value, select Encrypt value.

    The Add Variable dialog with a variable name and default value entered, and Encrypt value outlined

  6. Click Add.

  7. Click Update to save.

    The Default variables panel with new variables, one encrypted, Add Variable outlined, and the unsaved changes bar with Update outlined

A variable name starts with a letter or _ and can contain letters, digits, _, and -.

Changes stay pending until you click Update. The footer reads “You have unsaved changes”, and edited rows are marked “Edited, saved on Update”. To undo every pending change, click Cancel.

To copy or remove a variable, click the ellipsis icon (⋯) on its row, then click Clone row or Mark for deletion. Marked rows are removed when you click Update.

The JSON tab shows the variables as JSON, with encrypted values masked. Click Copy or Download to export them.

  1. On the Environments tab, click Create Environment.

  2. Enter an Environment name.

  3. (Optional) Describe where the environment points and who tests against it.

    The Create Environment dialog with Environment name outlined

  4. Click Create Environment.

The environment opens with every default variable. Its ID appears in its title. Inherited values are marked D.

  1. Click the value in the Value in column for the environment.
  2. Type the value this environment uses.
  3. Click Update at the top of the page.

The D mark disappears, and Environment properties shows how many of the values are overridden and how many are inherited. The ACTIVITY list records each override, with who made it.

An environment's page with an overridden value outlined, and the overridden count outlined under Environment properties

To go back to the default, click the ellipsis icon (⋯) on the row, click Reset value to default, then click Update.

Click Add Variable on the environment’s page. Enter the value this environment uses and a Default for other environments. Every environment gets the variable: the others start with the default value, and this one keeps its own.

  1. In the automated steps, click the value you want to replace.
  2. Open the Environment tab.
  3. Select a variable. Encrypted variables are marked secret.

The step now reads the variable as {env.<variable>}. To add or change variables from here, click Manage environments.

A Navigate to step's value picker with the Environment tab open, and the environment variables, including a secret one, outlined

If a variable’s name has a hyphen, write it in quotes and square brackets, for example {env["api-key"]}. With a dot, as in {env.api-key}, Arcus finds no value when the test runs.

When you start a Copilot session, choose the environment under Environment > Variables from in the Copilot configuration panel. The session reads its variables from that environment.

A recurring plan with an automated run template picks its environment under Automation Settings > Environment in the plan’s properties. Its runs read their variables from that environment. Leave it on the project’s default environment to follow the default. See Use automated templates.

The Environments tab lists each environment with its number of overrides under VARIABLES, the test plans that use it under USED IN, who created it, and when it was last changed. Sort by name, created date, or last modified.

The Environments tab listing an environment with its override count outlined, beside Default variables and Create Environment

Click the ellipsis icon (⋯) on a row for Edit, Clone, or Delete. To delete several, select their checkboxes and click Delete in the bar at the bottom.

  • Clone copies every value from the environment, including its overrides. The name is filled in with the original name and “copy”, so replace it before you click Clone Environment.
  • Delete removes the environment and its overridden values. The default variables stay.

Arcus doesn’t let you delete an environment that a test plan uses, or rename or delete a variable that a test case, step group, or API request uses.

Each environment’s page also shows LINKED TEST PLANS, its history, and an activity log of every change, with who made it.

Make a variable apply to one environment only

Section titled “Make a variable apply to one environment only”

Every variable exists in every environment. To make a value apply to one environment only, override it there and leave the default for the others.

The session used an environment that overrides the variable. Check Variables from in the Copilot configuration panel, and the variable’s value on that environment’s page.

Choose between an environment and a dataset

Section titled “Choose between an environment and a dataset”

Use an environment for values that change with where you test, such as URLs and accounts. Use a dataset for test data you want to repeat steps over.

Was this page helpful?