Configuration

danwo.config.ts default-exports one object. Every key is optional; defineConfig only types it.

import { defineConfig, stripeEnvironment } from "@danwo/sdk"

export default defineConfig({
  testDir: "tests",
  workers: 2,
  retries: 1,
  model: "anthropic/claude-sonnet-5",
  readiness: { mode: "page+backend", settle: true },
  video: "retain-on-failure",
  environment: () => stripeEnvironment(),
})

This page groups the options. Reference: Config lists each one with its type.

The config loads like a test file: Node removes its types and compiles nothing, so an enum or a namespace won't load. TypeScript in tests lists what works, imports included.

Types aren't checked either, so a misspelt key would do nothing. danwo warns about each key it doesn't know, and suggests the one you likely meant:

danwo: warning: unknown config key `retires` (did you mean `retries`?); danwo ignores it

Finding and running testsCopy Anchor Link

Split slow files across workersCopy Anchor Link

A worker runs one test file at a time, so one long file can keep one worker busy while the others sit idle. splitFiles: true (or danwo test --split-files) hands out single tests instead.

danwo only splits a file whose tests share nothing: no beforeAll or afterAll, and every test on isolation: "test". Other files still run whole. Each test loads its file again, so tests can't pass values to each other through variables at the top of the file.

What tests run againstCopy Anchor Link

WaitingCopy Anchor Link

The agentCopy Anchor Link

ReplaysCopy Anchor Link

Records and reportsCopy Anchor Link

The fault matrixCopy Anchor Link

matrix holds the matrix's own settings:

See Planning and budget for how the budget is spent.

NextCopy Anchor Link