Limited time

Sign up now and get one month free·No credit card required

Claim your free month
E2E tests from code changes

Meet O2!

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

Start with O2

Targeted test scope

Validates only what changed.

Self-updating test coverage

Keeps test cases aligned as the app evolves.

Autonomous test execution

Finds gaps, runs tests, and archives results.

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
Ship with confidence

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

FAQs

Frequently asked questions

Everything you need to know about DevAssure, PR testing, and CI integration.

DevAssure O2 is an autonomous testing agent for pull requests. It reads your code diff, maps the blast radius of the change, generates or updates the tests that matter, and runs them in CI—so teams ship without hand-writing or maintaining large script suites.

Yes. DevAssure offers a free starter option so you can validate your first PRs and try the workflow before upgrading. No credit card is required to get started.

DevAssure uses a context-aware engine. It does not only chase brittle selectors; it reasons about the intent of the UI. For multi-step checkouts, dashboards, and dense flows, O2 builds resilient tests that adapt as your UI evolves.

Install the CLI with npm (`npm install -g @devassure/cli`), add `devassure test` to your pipeline, or use the official GitHub Action from the GitHub Marketplace so every PR gets scoped validation on real browsers.

No. DevAssure fits into existing development and CI workflows. Teams can run it in the environments they already use for pull request validation and release checks.

Many suites re-run broad smoke tests on every change, which slows feedback. DevAssure uses impact intelligence to understand how a change affects user journeys, then validates only what is impacted—keeping QA fast while still catching regressions.

It acts as an AI-aware observer in your workflow. When you modify code, DevAssure maps the blast radius by tracing how those changes flow through dependencies. It then identifies, updates, or generates the specific tests needed to validate that change—surfacing regressions before merge.

Yes. DevAssure O2 can trigger when a pull request is created in GitHub. It analyzes the code changes, identifies impacted user flows, generates relevant tests, and executes what is necessary—without manual test authoring. You get actionable feedback in the PR so issues are caught early.

Yes. DevAssure can run inside GitHub Actions so pull requests are validated automatically in CI. Teams can start with the official GitHub Action or run the CLI in their existing pipeline.