test: add Playwright e2e regression net for current app#2
Draft
zphillips wants to merge 1 commit into
Draft
Conversation
Seven UI-level journeys (load, legend, story panel, track toggle, locate, help tips, reset hotkey) with mocked config + ER API for determinism. These assert behavior through the UI so they survive the planned Vite/React 19/ MapLibre overhaul. webpack-dev-server runs under --openssl-legacy-provider (Node 20 + webpack 4); tagged REMOVE-AFTER-VITE for removal in Pass 1.2. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a 7-journey Playwright regression net for the current app (network mocked) — a safety net before the React 19 / Vite / MapLibre modernization. No app code changes.
Decisions & alternatives
Appcomponent.--openssl-legacy-provider(Node 20 + webpack 4), taggedREMOVE-AFTER-VITE.Links
Tests — how do we know it's safe? (check all used)
Suite runs 7/7 green (
npx playwright test, self-contained, mocks config + ER API for determinism).Incident detection — if this breaks in prod, how will we know?
N/A — test-only, never shipped to users; breakage shows in CI / local runs, not production.
Incident impact analysis — can we measure the blast radius?
N/A — S4, no production surface.
Rollback & mitigation — if it goes wrong, how do we fix it fast?