Skip to content

CI & Pull Requests

Every pull request, verified on real devices before it merges.

Connect GitHub once. Every pull request then runs your scenarios on real devices, and the verdict lands in the PR.

Pull request #318

Swipeable onboarding

feature/onboarding → main · a41c9e2 · Swipeable onboarding

Buildsapp-release.apkApp.ipaPreview URL
duzz commented· Updating live0 passed · 0 failed · 0 running
Scenario · configAndroidiOSWeb
Sign upStaging · new user
OnboardingStaging · new user
CheckoutStaging · returning user

Open any result for its evidence

Checks

  • duzz (android)Waiting for the build
  • duzz (ios)Waiting for the build
  • duzz (web)Waiting for the build

Waiting for required checks

Open any result, then push a fix and watch the checks re-run

How it fits

Fits the way you already ship.

  1. Open a pull request

    Nothing changes in how you work.

  2. The build arrives

    Preview URLs or one CI upload step.

  3. Agents run on devices

    Every platform and configuration, in parallel.

  4. The verdict lands

    A check and a live comment in the PR.

  5. Merge with confidence

    A required check holds a failing change.

Setup

Set up once. Then it simply runs.

  • One GitHub App

    Pick repositories. Credentials are written for you.

  • Web previews

    Vercel, Netlify and Cloudflare Pages, no workflow file.

  • Mobile builds

    One readable upload step for your APK or IPA.

  • No runner waiting

    The job ends at upload. The check settles itself.

Coverage

Testing that matches the change.

  • Depth per branch

    Smoke on every PR, full regression into main.

  • A verdict per platform

    Android, iOS and web each gate on their own.

  • Coverage for the change

    DUZZ drafts a scenario from the PR for you to review.

  • Red means your app

    Our infrastructure issues never fail your check.

Results

The answer, where you review code.

  • The failing scenario, checkpoint and reason
  • A comment that updates live while runs play
  • Recording and logs one click away

Coding agents

The check step for coding agents.

An agent can upload its build, read the verdict and fix what failed, through DUZZ MCP.

  1. start_build_upload · build 1
  2. check_build · 3 runs in progress
  3. check_build · failed: Checkout on Galaxy S26 Ultra
  4. Agent fixes the promo total
  5. start_build_upload · build 2
  6. check_build · All settled: passed
Explore DUZZ MCP

Security

Least privilege, by design.

  • Repository scope

    You choose which repositories DUZZ sees.

  • Per-repo credentials

    Short-lived tokens, one credential each.

  • Write-only secrets

    We can write them, never read them back.

  • Your rules

    DUZZ never edits branch protection.

Put DUZZ on your next pull request.

We'll connect a repository and show your first verdict.