Setting Up Environments
Create and configure environments for your application
Set up environments to point your tests at staging, production, preview, or any other deployment target.
Creating an environment
- Open Environments & Auth in the sidebar.
- On the Environments tab, click Create Environment.
- Enter a name, the base URL, and pick a color.
- Save.
| Field | Description |
|---|---|
| Name | How the environment appears in run and monitor pickers |
| Base URL | The URL tests navigate to. Must be a valid https:// URL |
| Color | A color label for telling environments apart |
Base URL
The base URL is where every run against this environment starts. The agent opens it when a test begins, and relative navigation in your steps happens from there. Only https URLs are accepted.
Environment naming
Name environments after the deployment target so pickers stay unambiguous:
stagingandproductionfor long-lived targetspreview-pr-123for short-lived preview deploymentsqa-eu,qa-uswhen you test regional instances
Colors help too. A common trick is reserving red for production so it jumps out when you're about to start a run.
Environment configuration
Open an environment from the list to edit its name, base URL, and color.
Project credentials are managed on the Credentials tab of Environments & Auth, not per environment. See Auth & Credentials.
Managing environments
- Edit: open the environment and change any of its settings.
- Delete: click the trash icon in the environments list and confirm. Runs and monitors that reference the environment lose their target, so update any monitors that use it before deleting.
There's no default environment. Every run and monitor selects its environment explicitly, which keeps it obvious what each run actually targeted.