CI and GitHub

Run your tests and a fault matrix on every pull request. danwo reports back as a GitHub check, with an annotation on each failing test line, and keeps one comment on the pull request up to date.

The workflow复制标题链接

name: danwo
on: [pull_request]

permissions:
  checks: write
  pull-requests: write
  contents: read

jobs:
  danwo:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 24 }
      - run: npm ci
      - run: npx @danwo/cli install-browser --with-deps --only-shell
      - run: npx @danwo/cli test --reporter github
        env:
          GITHUB_TOKEN: ${{ github.token }}
      - run: npx @danwo/cli matrix tests/checkout.danwo.ts --reporter github
        if: ${{ !cancelled() }}
        env:
          GITHUB_TOKEN: ${{ github.token }}
      - uses: actions/upload-artifact@v4
        if: ${{ !cancelled() }}
        with:
          name: danwo-runs
          path: .danwo/runs

--reporter github turns on the check, the pull request comment and the job summary. The last step uploads the flight records, so you can open a failure's recording.

What the check shows复制标题链接

• pass and fail counts, and a row per failing test or fault;
• an annotation on each failing test line, in the pull request's Files changed tab;
• each failure's flight record, by its path in the uploaded artifact.

The same summary goes to the job summary page.

Several suites in one repository复制标题链接

A repository can hold more than one suite, such as an app's and its admin's. Give each a name, and GitHub reports each one on its own:

export default defineConfig({
  name: "admin",
  // …
})

--name admin on the command line does the same for one run. Upload each suite's runs under its artifact's name:

- uses: actions/upload-artifact@v4
  if: ${{ !cancelled() }}
  with:
    name: danwo-runs-admin
    path: admin/e2e/.danwo/runs

When git tracks more than one danwo config and a suite has no name, danwo names it after its config's folder, skipping folders such as e2e and tests. A repository with one suite reports as before.

Permissions复制标题链接

CI defaults复制标题链接

With CI set (every hosted CI sets it), or with --ci, danwo test:

• retries a failing test once;
• reads the replay cache without writing to it;
• refuses .only, with exit code 2 naming the file and line.

Your config's retries and --retries still win.

A danwo test that a test or fixture starts inherits the job's CI=true too. When that run is test data rather than a CI run of its own, pass --no-ci to give it the local defaults:

npx @danwo/cli test --no-ci

Setting CI=false in the child's environment does the same.

Make no model calls复制标题链接

A read-only cache still calls the model when a step has no recording. To make sure CI spends nothing, run with --replay-only:

npx @danwo/cli test --replay-only

Each agent step must then replay from the cache. A step that can't fails the test instead of calling the model:

✗ tests/checkout.danwo.ts › pays for an order  [Undecided]
  REPLAY_MISSING: agent.act("pay for the order") has no recording that replays (none was recorded), and replay-only runs no model. Run the test without --replay-only to record it, check it, and commit the cache.

4 passed, 1 failed (1 undecided)
cache: 11 replayed · 0 relocated · 0 handed off · 1 missed
model: 0 calls (replay-only)

To make every run replay-only, set it in the config:

cache: { dir: ".danwo-cache", replayOnly: true },

Record a failing step by running it locally without the flag, then commit the cache.

Bound the run复制标题链接

Two flags stop a run from starting new test files. Files already running finish:

Run npx @danwo/cli doctor as a first step to see what a run would trip on: Node, Chromium, the config, the model's key. --json prints the checks for a script.

For a config that runs its tests on devices, the doctor also checks each platform's toolchain. It finds them from the @danwo/mobile helpers the config calls:

Each failure says how to fix it. A config that runs on both platforms passes when one is ready, and the other's failures show as warnings.

Exit codes复制标题链接

Keep CI cheap复制标题链接

Run a narrowed matrix on pull requests with --faults, and the full matrix on a schedule.

Next复制标题链接