Introducing O2 Cloud Agents: Fully Managed Test Execution in the Cloud

QA Agents for Pull Requests

PR Native Testing Agent that watches code changes, maps impact, generates tests, and executes validation.

Cloud AgentExecution environments

Deploy fully managed Cloud Agents to execute, schedule, scale, and monitor your test suites on DevAssure's cloud infrastructure. No browser grids, runners, or infrastructure management required.

Launch Cloud Agent
Quick Demo
Input
branch/checkout → main
Scoped run
Changed files
18
Affected flows
9
Tests generated
27
1

Watches the code diff from branch comparison or commit.

2

Maps impacted user journeys and validation scenarios.

3

Discovers existing tests and identifies coverage gaps.

4

Generates missing tests and updates impacted ones.

5

Runs the session and exports results automatically.

Agent capabilities

Automated PR testing for
rapid releases.

O2 eliminates the slow loop between code review, QA triage, and execution by letting the agent own the entire test cycle.

01
Agent Reasoning

Impact Mapping

O2 instantly traces code changes to the affected user flows and components - ensuring complete validation coverage to the changed workflows.

02
Adaptive Coverage

Dynamic Test Generation

The agent automatically generates and executes end-to-end test scenarios from detected code changes—ensuring new functionality is always validated.

03
Agent-led execution

Zero-Maintenance Test Suites

Eliminate manual overhead. When your design evolves, the agent automatically synchronizes your test cases—intelligently updating logic or pruning obsolete paths in real-time.

04
Agent-led execution

From Push to Production

Connect your repo. O2 builds your pipeline. Ship with conviction. Monitor & iterate.

VS Code experience

Commit with Confidence

O2 ships as an interactive flow in the Tests view so teams can run change-focused sessions without leaving the editor.

Tests View

Test Branch

Diff source branch vs base

Test Commit

Target a specific commit ID

Commit ID (press enter to use current commit)
f2a1c9b | fix: checkout alignment
8d3e4a2 | feat: add promo codes
CLI command

Test directly from git code changes.

The command tells the agent which branch or commit to focus on so execution stays tied to the actual code delta.

devassure test
O2 release command
devassure test --path ./app --head feature/checkout-refactor --base main
# or
devassure test --commit 84db9f2 --environment staging --headless true
--archive ./reports · --url https://staging.example.com

Product surface

Short demos for each surface your team already uses.

O2 fits into the tools developers already trust, so the workflow stays familiar while the testing becomes more intelligent.

O2 in GitHub Actions

Seamlessly integrate O2 into your CI/CD pipelines.

Seamless across dev surfaces
Ship with confidence

Release faster with an agent that understands the application before it tests.

FAQs

Frequently asked questions

How O2 generates tests from diffs, where results land, and whether you need an existing suite.

O2 is a managed testing agent that reads your pull request diff, maps which user flows could break, generates or updates the tests that matter, and runs them in real browsers. You get pass/fail results on the PR without writing or maintaining a script suite.

No. O2 generates executable coverage from the change itself. Teams with an existing Playwright or Cypress suite can keep those jobs running in parallel; O2 does not require you to import or rewrite them.

Results post back to the pull request with pass/fail status, screenshots, and a shareable session report. Failures are attached to the change that caused them, so developers fix issues before merge instead of after release.

O2 starts from the code diff — not a full-suite replay. It traces how changed files flow through the application, identifies impacted journeys, and executes only those tests. Unrelated smoke and regression coverage is left out so feedback stays fast.

Yes. You can describe flows in plain English or YAML. O2 executes those alongside auto-generated coverage, so you can pin revenue-critical paths while the agent keeps up with new diffs.

Yes. Configure the environment and credentials once — O2 authenticates, then runs the impacted flows in a real browser. Named environments (staging, QA, production) can be selected per job without changing test cases.