17 lines
1.3 KiB
Markdown
17 lines
1.3 KiB
Markdown
# Tip #10 — Playwright E2E smoke tests
|
|
|
|
**Date:** 2026-06-21
|
|
**Category:** devex
|
|
**Source:** MC-Survival Wiki Daily Tip (backfilled from state.json)
|
|
**Note:** *Title was truncated in the original state.json log. Body matches the 'Search-Synonyms alias table' variant of the same idea.*
|
|
|
|
## Playwright E2E smoke tests
|
|
|
|
Stand up Playwright with a minimal smoke-test suite — home loads, recipe page renders, editor login works — running on every pull request via GitHub Actions. It solves the no-coverage problem: today every release is a manual test, and the result is a steady trickle of regressions that get caught in production by users. The signal is operational reality — the project has zero automated tests, which is fine for a prototype and unacceptable for a wiki other people depend on. Starting with three smoke tests, not 30, is the right scope: a single homepage-screenshot test catches the majority of 'it broke' regressions at near-zero maintenance cost.
|
|
|
|
## Implementation tips
|
|
|
|
1. Add @playwright/test as dev-dep, scaffold playwright.config.ts, write 3 tests: home loads, recipe page renders, editor login works.
|
|
2. Run in CI on every PR (GitHub Actions: ubuntu-latest, npm ci, npx playwright install --with-deps, npx playwright test).
|
|
3. Start with the homepage screenshot test — cheapest, catches 80% of 'it broke' regressions.
|