Before reading this article: Environments and Auth Profiles are part of AIDEN, Qase's AI-powered cloud test execution engine. If you're new to AIDEN, we recommend reading this article first.
Introduction
Environments define where your tests run. Auth Profiles define how they authenticate. Together, they let AIDEN's cloud test execution target the right host with the right credentials, no manual credential handling needed.
With Environments, you configure the URLs of your application (staging, production, feature branches).
With Auth Profiles, you store login credentials and link them to those environments.
When you launch a cloud test run, AIDEN automatically injects the right credentials for the selected environment.
Environments
Environments represent the different deployments of your application, staging servers, production instances, feature branch previews, and more. Defining them in Qase lets you run tests against any target without hardcoding URLs.
Creating an Environment
1. Navigate to Environments in your project.
2. Click Create new environment
3. Fill in the following fields:
Title (required) — A human-readable name for the environment, e.g., "Production"
Slug (required) — A short identifier, e.g., prod. Must be unique within the project.
Description (optional) — Supports Markdown. Use it to document the environment's purpose or access instructions.
Environment type (radio selection):
Dynamic (Recommended) — Automatically matches environments by host pattern (e.g., *.feature.company.com). Ideal for feature branches, preview builds, and CI deployments.
Static — Points to a single static URL. Best for stable environments like staging or production.
Host pattern — For static environments, enter a concrete URL (e.g., staging.example.com). For dynamic environments, enter a wildcard pattern (e.g., *.stage.example.dev).
Click Save.
Note: Dynamic environment host patterns must contain at least one * wildcard and one . dot. Consecutive wildcards (**) are not allowed.
Valid examples: *.stage.example.dev, *.myapp.com.
The Environment Card List
Environments are displayed in a card-based layout. Each card shows:
A type tag (Static or Dynamic)
The environment title
The host URL
For dynamic environments: the instance count (e.g., "3 instances")
For static environments that match a dynamic pattern: "Instance in <parent name> *<parent host>"
Each card has quick-action buttons that appear on hover:
Run — Launches a test run against that environment (static environments only)
Edit — Opens the edit modal
Delete — Removes the environment
Copy host — Copies the host URL to your clipboard
The Environment Sidebar
Click any environment card to open the detail sidebar on the right. The sidebar displays:
Type tag (Static or Dynamic) and the environment title
Host (labeled "Host pattern" for dynamic environments, "Host" for static)
SlugAuthorization profiles section — Lists all linked auth profiles with their credentials. Passwords are masked by default (shown as - - - - - - - - ).
Unlink button per profile — Removes the link between the profile and this environment. For generated profiles, a confirmation dialog warns that credentials will be removed.
Test run history — Shows recent runs with status icons (passed, failed, aborted, in progress). For dynamic environments: a list of all matched static instances
Auth Profiles
Auth profiles store authentication credentials for automated test execution. Instead of entering login details every time you run a test, you create a profile once and reuse it across runs.
Overview
The Auth Profiles page shows a table of all profiles with columns for title, auth type, and linked environments.
You can filter by auth type and search by name.
Supported Auth Types
Auth Type | Label in UI | Credential Fields |
Web (Login/Password) | Web (Login/Password) | login, password |
API Key | API | api_key |
HTTP Basic | HTTP Basic | username, password |
Note: All credentials are encrypted at rest using AES-256. Credential values are masked in the UI by default.
Creating an Auth Profile:
Creating an auth profile is a two-step process.
Step 1: Configure profile:
Click New profile on the Auth Profiles page.
Enter a Title (required) — e.g., "Admin"
Select an Auth type (required) — choose from Web (Login/Password), API, or HTTP Basic.
Under Link environment, select one or more environments to link. Dynamic environments show their instance count in the dropdown.
A summary of linked environments appears below the selector.
Click Set credentials to proceed.
Step 2: Enter credentials:
For each linked environment, enter the credential fields appropriate to the selected auth type (e.g., login and password for Web auth).
A summary card at the top shows the profile title, auth type, and linked environments.
Choose a save option:
Save draft — Stores the profile without triggering generation. The profile status becomes
Draft.Save & Generate — Stores the profile and immediately triggers automated browser recording. The profile status becomes
In Progress.
Profile Statuses
Status | Meaning |
Draft | Created but not generated. Cannot be used for test execution yet. |
In Progress | Automated generation is currently running. |
Success | Ready to use in test runs. |
Error | Generation failed. Can be retried via the Regenerate action. |
Important: Only profiles with Success status can be used in test runs. Draft or errored profiles must be generated (or regenerated) before they can be selected.
The Auth Profile Sidebar
Click any profile row to open the detail sidebar. The sidebar shows:
Auth type label and profile title
Draft warning with a Generate button (shown when the profile status is
Draft)Generation status — Live progress with numbered steps, status indicators, and screenshots (shown during and after generation)
Credentials per environment — Editable inline. You can add, modify, or remove credential fields for each linked environment.
Link environment button — Opens a selector to link additional environments
Unlink button per environment — Removes the environment link and its credentials
Footer with Delete and Save buttons
Generation Progress
When generation starts, the sidebar shows live progress. Each step displays:
A step number
The step text describing the action (e.g., "Open login page")
A status indicator (success or failure)
If generation fails, the profile status updates to Error with a description of the problem. You can regenerate at any time by clicking the restart button in the sidebar.
Linking Environments and Auth Profiles
Environments and auth profiles have a many-to-many relationship. Each environment can have multiple auth profiles, and each auth profile can store different credentials per environment (e.g., admin credentials for staging, read-only credentials for production).
You can create links from two places:
From an environment card: Open the sidebar, then use the action to link an auth profile. Select the profile and enter credentials.
From an auth profile sidebar: Click + Link environment, select an environment from the dropdown, and credentials are created for that environment.
Credential Fallback for Dynamic Environments
When tests run against a static environment that has no credentials of its own, the system automatically checks if any dynamic environment's wildcard pattern matches that static host. If a match is found, credentials from the dynamic environment are used.
Here's how it works:
You create a dynamic environment
*.myapp.comand link an auth profile with credentials.You create a static environment
staging.myapp.combut do not link any credentials to it.When you run tests against
staging.myapp.com, the system sees it has no direct credentials.It checks dynamic environments and finds that
*.myapp.commatchesstaging.myapp.com.The credentials from
*.myapp.comare used automatically.
Using Auth Profiles in Test Execution
When creating a cloud test run, you can select one or more auth profiles to use for authentication.
The auth profile selector is a multi-select dropdown that shows each profile's name, auth type, and status. Only profiles linked to the selected environment are shown.
Profiles that are not yet generated display a warning: "Profile is not generated" with a link to the Auth Profiles page.
Profiles currently generating show: "Generation in progress".
Prerequisites for using auth profiles in a run:
Your target environment must have at least one linked auth profile with status
Success.Create a test run and select the target environment.
Select the auth profile(s) to use from the multi-select dropdown.
Launch the run — credentials are injected automatically.
