New in DevAssure O2: Scriptless Flutter Web Testing + TestRail Integration·

Pull request testing

Automated Pull Request Testing for GitHub

Validate every code change before merge — without writing or maintaining test scripts.

Start testing your PRs

What is pull request testing?

Pull request testing is the practice of automatically validating every code change before it merges, by running targeted tests against the specific flows a PR could affect. Instead of waiting for a full regression suite or manual QA pass, teams get fast, scoped feedback on the exact risk introduced by each pull request.

Why PR testing breaks down without automation

  • Teams scale PRs faster than QA can keep up
  • Regression suites test everything, not what changed
  • Scripts break when UI changes; nobody maintains them

How DevAssure O2 handles PR testing

When a pull request opens in GitHub, O2 triggers automatically. It analyzes the diff, maps the blast radius of the change, generates tests for impacted flows, executes them in CI, and posts results as a PR comment — so developers fix issues before merge.

Step 1

Diff analysis

O2 reads changed files, affected logic, and related modules in the pull request.

Step 2

Blast radius mapping

O2 builds an impact map of user flows and risky dependencies touched by the change.

Step 3

Test generation

O2 creates fit-for-change tests for impacted flows — not your full regression suite.

Step 4

Execution

Only the mapped flows run on real browsers in your CI pipeline.

Step 5

PR comment with results

Pass/fail status, screenshots, and actionable feedback are posted directly on the PR.

Triggered on every pull request

Set up PR testing in GitHub Actions

Add the DevAssure GitHub Action to your repository. Paste the workflow below, add your DEVASSURE_TOKEN secret, and O2 will test every pull request automatically.

.github/workflows/devassure.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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 }}

For setup details, troubleshooting, and advanced configuration, see the full GitHub Actions documentation.

PR testing vs regression testing — what's the difference

PR testing validates only the user flows affected by a specific pull request's code changes, giving fast feedback before merge. Regression testing runs a broader suite against the full application — typically on a schedule or before release. DevAssure O2 bridges both: it scopes testing to what changed in each PR while still catching regressions in the impacted areas, without re-running your entire suite on every commit.

See how DevAssure O2 compares to QA Wolf and Playwright for teams evaluating their options. Compare DevAssure O2 vs QA Wolf or Compare DevAssure O2 vs Playwright.

Start testing your PRs

Join teams using DevAssure O2 to catch bugs before merge. Free to start — no credit card required.

Start testing your PRs

Frequently asked questions

Most DevAssure O2 runs finish in under 30 minutes because only flows impacted by the pull request are tested — not your entire regression suite. Run time scales with the blast radius of the change, not the size of your application.

No. DevAssure O2 reads your PR diff, maps which user flows could be affected, and generates the tests automatically. You do not need Playwright scripts, Cypress specs, or a pre-built test library to get started.

Yes. DevAssure ships an official GitHub Action that drops into your existing workflow. Add one YAML file and a DEVASSURE_TOKEN secret — no framework migration required. O2 also supports GitLab CI and CircleCI via the CLI.

O2 posts results directly on the pull request with pass/fail status, screenshots, and session details. Developers see exactly which flow broke and why — before the code merges — so issues are fixed in context instead of after release.

No. DevAssure O2 handles the automated validation of code changes on every PR — it generates and runs targeted tests so your team does not have to write or maintain test scripts. QA engineers can focus on exploratory testing, edge cases, and quality strategy instead of script maintenance.

Blast radius refers to the set of user flows and application areas that could be affected by a specific code change. DevAssure O2 maps the blast radius of every pull request by tracing how changed files flow through dependencies, then runs tests only on the impacted flows.