Skip to main content

AgentsDirect link to Agents

An agent is a single execution unit — it runs one test session at a time, in an isolated browser environment. Your account's agent count is shown under your account name in the sidebar (e.g. O2 Agent) and determines how many test sessions can run in parallel.

How Cloud Agents workDirect link to How Cloud Agents work

You don't provision or configure Cloud Agents directly. When you start a test session:

  1. DevAssure allocates an available agent from your fleet.
  2. The agent spins up an isolated, ephemeral browser environment in the cloud.
  3. It executes your test case's steps against the selected environment.
  4. On completion (pass, fail, or cancellation), the agent tears down. No state, cookies, or test data persist between sessions.

This means there's no maintenance window, no browser version to patch, and no leftover state to clean up between runs.

Checking agent availabilityDirect link to Checking agent availability

The Dashboard shows your fleet at a glance: a row of agent icons plus a summary like 8 available · 0 busy. A busy agent is actively executing a session; an available agent is idle and ready to pick up the next run.

If you start more test sessions than you have available agents, additional sessions queue and start as agents free up — they aren't dropped or failed.

Increasing parallelismDirect link to Increasing parallelism

Each agent can only run one session at a time, so total parallel throughput is capped by your agent count. To run more simultaneously (for example, to keep a large regression suite fast), add agents from Settings → Agents or Upgrade in the top navigation.

Self-hosted agentsDirect link to Self-hosted agents

If an environment isn't reachable from the public internet (an internal staging server behind a firewall or VPN, for example), you can run a self-hosted agent on your own network instead of using DevAssure-managed Cloud Agents:

  1. Go to Self hosted in the left navigation.
  2. Follow the setup instructions to install and register a local agent against your account.
  3. Once connected, the self-hosted agent appears alongside your Cloud Agents and can be targeted the same way when launching a test session.

This gives you a hybrid setup: public-facing environments run on fully managed Cloud Agents, while internal environments run through your own infrastructure — without maintaining two separate tools.

  • Environments — what agents execute against.
  • Test Sessions — where you see which agent ran a given session, and for how long.