Production

On production, danwo checks that your main pages work after a deploy. It drives a real browser against the live site and records what it saw. It emulates nothing and breaks nothing: production is for smoke tests only.

Set it upCopy Anchor Link

Point danwo at the live site with baseUrl, and no environment. With no environment there's no proxy, so nothing can be faulted by accident:

import { defineConfig } from "@danwo/sdk"

export default defineConfig({
  testDir: "tests/smoke",
  baseUrl: "https://example.com",
})

Keep smoke tests in their own folder, and keep them short: the home page loads, a test user can sign in, the main page they need shows.

import { test } from "@danwo/sdk"

test("the home page loads", async ({ app, screen, expect }) => {
  await app.open("/")
  await expect(screen.getByRole("link", { name: "Sign in" })).toBeVisible()
})

npx @danwo/cli test --config danwo.production.config.ts

Rules for productionCopy Anchor Link

• Read, don't write. Don't buy, send or delete anything a real customer would see.
• Use a dedicated test account, created for this, with its password in secrets.
• Never run danwo matrix here. It refuses anyway: with no environment, there's no proxy to put faults in.
• No emulators. Production must talk to the real services.

Running it on a scheduleCopy Anchor Link

danwo doesn't have scheduled monitoring yet. Run the smoke tests from your CI after each deploy, or on a timer in your CI's scheduler.

NextCopy Anchor Link