Automatically Test Every GitHub PR Before Merge.
DevAssure O2 reads your code changes, generates tests, and validates impacted flows — without writing or maintaining test scripts.
GitHub PR Testing Demo
Watch O2 on a GitHub pull request, identifying what could break, generating tests, and reporting issues before merge.
Automated Pull Request Validation
From the moment you make a code change, O2 starts working in the background of your GitHub PR.
PR Created
A pull request opens in GitHub and triggers O2 automatically.
Context Analysis
O2 inspects changed files, affected logic, and related modules.
Impact Mapping
O2 builds an impact map of user flows and risky dependencies.
Test Generation
O2 creates fit-for-change tests instead of stale suites.
Smart Execution
Only impacted flows are executed, reducing unnecessary runtime.
Actionable Insights
Failures are surfaced as actionable PR feedback before merge.
Live Diff Analysis
checkout/address.tsx+14 linespayment/summary.ts+9 linesImpact analysis detected a logic conflict in coupon recalculation when paired with saved profiles.
Start testing PRs with GitHub Actions.
Add O2 to your existing GitHub Actions pipeline.
No framework migration, no script maintenance, no setup.
name: devassure
on: [push]
jobs:
e2e:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
ref: ${{ github.head_ref || github.ref_name }}
- uses: actions/setup-node@v4
with:
node-version: "24"
- name: Run DevAssure
uses: devassure-ai/devassure-action@v1
env:
DEVASSURE_TOKEN: ${{ secrets.DEVASSURE_TOKEN }}DEVASSURE_TOKEN to repo secrets•Runs on the next pushRaise a PR. O2 does the rest.
O2 maps the impact of your code changes, then generates and executes targeted tests in real time.
CI/CD Pipeline
Linear, fragile, and developer-heavy.
DevAssure O2
Autonomous, impact-aware PR validation.
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.
Ready to test your PRs automatically?
Stop writing tests. Start validating changes.