Skip to main content

Environments

Define where your application is deployed — staging, production, feature branches — and record which environment each test run targeted.

Environments represent the deployments of your application that you test against — staging servers, production instances, feature-branch previews. Defining them in a project lets every test run record where it was executed, and lets you start a run against a specific environment in one click.

Authorization profiles, which stored login credentials for AIDEN's cloud test runs, retired on November 6, 2026 together with AIDEN's test automation. Environments themselves are not affected. Retiring AIDEN's test automation explains what changed.

​

​

Creating an environment

  1. Open your project and select Environments in the project sidebar.

  2. Click New environment.

  3. Fill in the fields described below, then click Save.

Field

What it is

Title (required)

A human-readable name, for example "Production".

Slug (required)

A short identifier, for example prod. It must be unique within the project.

Description

Optional, and supports Markdown. Use it to note the environment's purpose or access instructions.

Environment type

Dynamic (Recommended) matches environments by a host pattern, which suits feature branches, preview builds and CI deployments. Static points to a single URL, which suits stable environments such as staging or production.

Host pattern / Host

For a static environment, a concrete URL such as staging.example.com. For a dynamic environment, a wildcard pattern such as *.stage.example.dev.

​

A dynamic host pattern must contain at least one * wildcard and at least one dot. Two wildcards in a row are not allowed.

​

The New environment form with Title, Slug, Description, Environment type and Host pattern

​

​

The environment list

Environments appear as cards. Use Search environments to find one by name, or Add filter to narrow the list. Each card shows:

  • A type tag, Static or Dynamic

  • The environment title

  • The host, with a button that copies it to your clipboard

  • The slug

  • The most recent test run against the environment, or "Not executed yet"

  • For a dynamic environment, how many static environments match its pattern

​

Hover over a card for its quick actions:

  • Run opens the test run form with this environment already selected. It is available on static environments only.

  • Edit opens the environment for editing.

  • Delete removes the environment.

​

​

The environment sidebar

Click a card to open its details on the right. The sidebar shows the type, title, host (labelled Host pattern for a dynamic environment), slug and description, followed by the environment's recent test runs with their status. For a dynamic environment it also lists the static environments that match its pattern.

​

​

Using environments in test runs

When you create a test run, pick the environment in the Environment field. The run then shows its environment in the run details, and the run appears in that environment's history. Test runs covers the rest of the run form.

​

When you create runs from a pipeline, refer to an environment by its slug. The Qase CLI, for example, takes it as --environment followed by the slug.

​

​

FAQ

What happened to authorization profiles?

​

They retired on November 6, 2026, with the rest of AIDEN's test automation. They existed only to log AIDEN's cloud test runs in to your application, so they went when those runs did. The Authorization profiles page and the profile links on environment cards are no longer shown.

​

Do I need to recreate my environments?

​

No. Every environment you created is still there, with its host, slug and run history.

Did this answer your question?