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
Setup, secrets, branch protection, and running O2 next to your existing GitHub Actions jobs.
Add `devassure-ai/devassure-action@v1` to a workflow that runs on pull_request, then store a DEVASSURE_TOKEN as a repository secret. One YAML file is enough — O2 analyzes the diff, runs targeted tests, and posts results on the PR.
Yes. Keep your current workflow steps and add O2 as a separate job. Many teams leave Playwright for legacy or highly custom flows and let O2 cover new surface area on every PR until they are ready to shrink the hand-written suite.
Yes. The Action runs in your GitHub Actions environment against private repositories. Code analysis happens as part of the workflow; you are not asked to upload the repo to a separate dashboard to get started.
The Action needs a DEVASSURE_TOKEN secret for authentication. It runs on standard GitHub-hosted Ubuntu runners and posts a check plus a PR comment. You do not need to install browsers, drivers, or a grid on the runner.
O2 reports a failing GitHub check when a generated or authored test fails. You can require that check in branch protection so a red O2 run blocks merge the same way lint or unit tests do.
Most PR runs finish in under 30 minutes because O2 tests the blast radius of the change rather than the full suite. Duration scales with how much the PR touches, not with the size of your entire application.
Ready to test your PRs automatically?
Stop writing tests. Start validating changes.