Limited time

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

QA Agents for PRs.Built around real user journeys.

DevAssure's O2 is a PR-native testing agent that maps how each code change affects user journeys, generates or updates the right checks, and runs them in CI before merge.

One Install. Every Environment
IDEExtension

Install the DevAssure O2 extension in your editor of choice — VS Code, Cursor, or Anti Gravity.

devassure — bash — ~/project
● ready

How it works

Understand. Map. Validate.

Step 0101
checkout.ts+47 / -12
+ discount logic rewritten
- old_discount_calc()

Reads your code change

Starts from the diff and builds context from files, functions, and dependencies.

Step 0202
process_order
checkout — AFFECTED
inventory — WATCH
email_service — SAFE

Maps the blast radius

Traces the change to the screens and user journeys most likely to be affected.

Step 0303
Git
P0 Bug Detected
test_payment_retry_flow

Validates and executes

Generates or updates checks, then runs them before merge with actionable results.

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

Every code change, tested before merge.

128 hr/moQA Time Saved
~0Test Maintenance
100%Reliable Test Runs
2xFaster Releases

How DevAssure sits next to recognized QA practice

O2 is built for teams that already follow continuous integration, layered testing, and accessibility expectations from the broader industry—then removes the busywork of authoring and babysitting brittle suites for every PR.

The “Test Pyramid” is a metaphor that tells us to group software tests into buckets of different granularity. It also gives an idea of how many tests we should have in each of these groups.
— Ham Vocke, The Practical Test Pyramid (martinfowler.com)

At a glance: Install the public CLI with npm install -g @devassure/cli, list the package on npm, and add the DevAssure GitHub Action from the Marketplace to a workflow file.

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.