---
title: "Test Environments"
description: "Define the named configurations that test plans and suites use during execution."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.heizen.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Test Environments

Test environments describe where a run executes. Give each environment a clear
name such as Development, Staging, or Production and store the configuration
needed by the test runner in that environment.

![Heizen Studio Test Environments page showing environment cards, descriptions, configuration counts, and Create Environment action.](/images/heizen-studio/environment.png)

## Create an environment

1. Open **QA Agent → Test Environments**.
2. Choose **Create Environment**.
3. Enter a name and optional description.
4. Open the environment to add or edit configuration values.

Use one environment per meaningful target. Do not create a new environment for
every run unless the target or credentials actually differ.

## Use an environment in execution

Select an environment when running a suite or plan, or set a default environment
on the plan. If the runner asks for environment details, verify the selected
environment before starting the run.

## Protect credentials

Use [project Secrets](/studio/secrets) for sensitive values and keep the
environment configuration limited to the references or non-sensitive settings
the runner needs. Never paste production credentials into a test case title,
description, or screenshot.

> **Environment names are operational context**
>
> A test result without its environment is difficult to interpret. Treat a
> rename or configuration change as a meaningful QA change and communicate it to
> the team.

Source: https://docs.heizen.work/studio/qa/environments/index.mdx