bert.hausmans
b8d18e63af
B1 of TEST-INFRA-001 (RFC-WS-FRONTEND-PRIMEVUE Amendment A-1).
- Add @playwright/test, @playwright/experimental-ct-vue,
@axe-core/playwright as dev deps in apps/app
- Add @vue/compiler-dom (transitively required by ct-vue's Vite build
pipeline; not auto-resolved on Vite 7)
- Install Chromium via `playwright install chromium` (host cache only,
not committed)
- Configure Git LFS clean/smudge filters globally; track
apps/app/tests/playwright-{ct,e2e}/__screenshots__/**/*.png
- Integrate `git lfs pre-push` into lefthook.yml since LFS's per-repo
hook would conflict with the existing sync-staleness hook
- Add playwright/index.html + playwright/index.ts hook file with the
full provider stack (Vuetify [TEMPORARY: replaced in F3 by PrimeVue],
Pinia, TanStack Vue Query, memory-history Router with no auth
guards)
- Add playwright.config.ts (e2e, Chromium-only, baseURL :5173, auto-
starts `pnpm dev` via webServer)
- Add playwright-ct.config.ts (component testing, Linux-Chromium-only
baselines, maxDiffPixelRatio 0.001, snapshot path template,
ssr.noExternal: ['vuetify'] mirroring vitest.config.ts)
- Add scripts: test:component, test:e2e, test:visual,
test:visual:update
- Add smoke test proving Chromium boots in the CT runner
- Update .gitignore for Playwright runtime artifacts (test-results/,
playwright-report/, blob-report/, playwright/.cache/)
Vitest's existing 402 tests still pass unchanged.
DoD-17 / DoD-19 CI integration deferred to TEST-INFRA-002 per Amendment
A-1 scope cut (no CI exists in this repo today).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
39 lines
1.6 KiB
YAML
39 lines
1.6 KiB
YAML
# Lefthook configuration.
|
|
#
|
|
# Replaces the hand-rolled scripts that previously lived under
|
|
# .githooks/ and were registered via `git config core.hooksPath
|
|
# .githooks`. Behaviour is intentionally 1:1 with those scripts —
|
|
# see WS-3 session 1a notes for the migration record.
|
|
#
|
|
# The .githooks/ scripts remain on disk and contain the actual logic
|
|
# (gating against .claude-sync.conf, merge-commit handling, the
|
|
# non-blocking pre-push warning). lefthook dispatches to them so the
|
|
# delicate gating logic isn't re-translated into YAML. See
|
|
# .githooks/README.md for details.
|
|
|
|
post-commit:
|
|
commands:
|
|
sync-claude-docs:
|
|
run: bash .githooks/post-commit
|
|
|
|
pre-push:
|
|
commands:
|
|
sync-check:
|
|
run: bash .githooks/pre-push
|
|
# Manual smoke tests need `lefthook run pre-push --force`:
|
|
# without `--force`, lefthook v2 inspects {push_files} (the
|
|
# diff between local and remote) and skips when that list is
|
|
# empty, which is always the case during a manual run. On a
|
|
# real `git push` with commits the file list is non-empty and
|
|
# the command fires — matching the legacy hook's "always runs"
|
|
# behaviour. (Pushing with zero new commits would be skipped
|
|
# under lefthook but is a no-op for the sync-staleness warning
|
|
# anyway, so behaviour stays effectively 1:1.)
|
|
git-lfs:
|
|
# `git lfs install --skip-repo` only sets up global clean/smudge
|
|
# filters — it does NOT install the per-repo pre-push hook
|
|
# (which would conflict with lefthook). We delegate the LFS
|
|
# upload step here so screenshot baselines tracked via LFS get
|
|
# pushed alongside their commits.
|
|
run: git lfs pre-push {1} {2}
|