Environments

An environment represents one target application (or one meaningful slice of an application) that cloud agent runs tests against. Every test session runs against exactly one environment.

Creating an environment

1. Go to Environments in the left navigation.
2. Click Add Environment.
3. Fill in:
   • Name — internal label shown across the app (dashboard cards, session tables, test case assignment).
   • URL — the starting point O2 loads for any test case step that begins with load the url.
4. Save.

There's no environment limit tied to plan tier by default — create as many as your application surfaces warrant. Common patterns:

• One environment per deployment stage: production, staging, dev.
• One environment per critical flow, if you want isolated health tracking: checkout, onboarding, admin-console.

Editing or removing an environment

Open Environments, select an environment, and use the overflow menu to rename, update the URL, or delete it. Deleting an environment does not delete its historical test sessions, but you won't be able to launch new sessions against it.

Health score

Each environment shows a score from 0–100 on its card in Environments and on the Dashboard. The score reflects how recent test sessions against that environment have performed:

• 70–100 (green) — recent sessions are largely passing.
• 50–69 (amber) — mixed results; worth a look.
• Below 50 (red) — recent sessions are failing more often than not.

The score updates automatically as new sessions complete against that environment — there's nothing to configure.

Environments and Cloud Agents

Environments and agents are independent: any available Cloud Agent can execute a test session against any environment. You don't assign specific agents to specific environments. If an environment sits behind a firewall and isn't reachable from DevAssure's managed infrastructure, see Self-Hosted Agents to run it through your own network instead.