Skip to content

Kiln-AI/Kiln / .agents/skills/playwright

playwright

Verified

Look at Kiln's UI in a real browser, and run its end-to-end tests. Use when checking UI you are changing, taking a screenshot of the app, driving the app with playwright-cli, starting the dev sandbox with playwright_server.sh, running or debugging `npm run tests:e2e`, or working with the seeded fixture project that gives the app's screens data to render.

references/e2e_suite.md

View on GitHub
# Running the e2e suite

From `app/web_ui`:

```bash
npm run tests:e2e                                    # everything
npx playwright test tests/e2e/act_sanity.spec.ts     # one spec
npx playwright test tests/e2e/act_sanity.spec.ts -g "install verification"
npx playwright test --reporter=line                  # readable in a terminal
```

You do not start anything first. `playwright.config.ts` boots four servers itself
and shuts them all down at the end:

| Server | What it is |
|---|---|
| `uv run python -m app.desktop.dev_server` | the real Python backend |
| `vite dev` | the web UI |
| `tests/e2e/mock_provider` | a stand-in inference provider, so no test calls a real model |
| `tests/e2e/mock_kiln_server` | a stand-in for api.kiln.tech |

Two consequences worth knowing before you debug a failure:

- **The suite is serial.** `fullyParallel: false` and `workers: 1`, because every
  test shares one backend. A test that leaves state behind can break the next one.
- **It cannot touch your real Kiln data.** The backend runs with `HOME` pointed at
  `app/web_ui/.e2e_home`, which is wiped on every run. The suite also sets
  `reuseExistingServer: false`, so it will not attach to a server you already
  have running — and will fail if one is holding its ports (6534-6537).

## Reading the report

The default reporter is `html`. After a run:

```bash
npx playwright show-report            # opens a browser; needs a display
```

In a container, read the files directly instead. For each failure Playwright
writes an accessibility snapshot of the page at the moment it gave up:

```bash
cat test-results/<test-name>/error-context.md
```

That snapshot is usually enough on its own — it shows whether the element was
missing, renamed, or covered by something else. `--reporter=line` gives you the
failure text without generating a report at all.

## First run on a route can be slow

`vite dev` compiles a route the first time a test navigates to it, and that
compile can take several seconds on a cold checkout. Assertions using the default
5 s `expect` timeout can lose that race, so a test that fails once and passes on a
re-run is usually this rather than a real bug. `--repeat-each=2` tells the two
apart: cold-compile failures fail the first repetition and pass the second.

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall