Skip to main content

Environments

Environments help teams indicate where a test run was executed (e.g., Staging, Production, Chrome, Device Lab).

Creating environments​

Provide:

  • Name – Displayed in run forms and analytics.
  • Host/URL (optional) – Useful for linking to deployed hosts or device farms.
  • Description – Note configuration details, credentials, or setup instructions.

Environments are project-specific so teams can tailor the list to their needs without affecting other projects.

Usage​

  • Select an environment when launching manual or automated runs.
  • Filter analytics, dashboards, and exports by environment to compare results.
  • Include environment metadata in automated test run payloads so pipeline results stay aligned.

Tips​

  • Keep the list concise—too many options slows down run creation.
  • Pair environments with configuration options (browser, locale) for richer reporting.
  • Update descriptions when hosts change to keep onboarding docs accurate.