23 lines
940 B
Markdown
23 lines
940 B
Markdown
# ADR-0003: Keep Browser Testing Resources Project-Local
|
|
|
|
Status: Accepted
|
|
Date: 2026-07-14
|
|
|
|
## Context
|
|
|
|
Browser tests and diagnostics run in a headless Debian development container. The toolchain needs repeatable versions and repository-scoped resources.
|
|
|
|
## Decision
|
|
|
|
- Use Playwright Test with bundled Chromium for repeatable E2E tests.
|
|
- Keep E2E tests separate from `npm run check` because browser installation is an explicit setup step.
|
|
- Run Chromium headlessly with profile isolation and sandboxing.
|
|
- Store npm and browser caches under `.cache/`.
|
|
- Store traces, screenshots, videos, and CLI output under `.artifacts/`.
|
|
|
|
## Consequences
|
|
|
|
- A fresh environment installs npm dependencies, browser libraries, and the pinned Chromium revision before browser work.
|
|
- Browser failures can retain diagnostics without adding generated files to source control.
|
|
- Repository configuration controls browser versions and artifact locations.
|