Sprint 2 batch 7: Playwright e2e smoke for auth UI + 404 page#127
Merged
Conversation
Spins up next dev on :3100 (output: standalone makes next start a no-op,
and the standalone build embeds an absolute path that differs between
local and CI), then runs three checks:
1. login page exposes the email/password inputs we just rewired with
proper htmlFor — clicking the visible label focuses the input.
2. forgot-password has the same label/input pairing.
3. an unknown route under /login/* yields HTTP 404 + the branded
not-found.tsx (heading + dashboard link).
The playwright.yml workflow runs on push/PR and uploads the report on
failure. Local: 3/3 passed.
keysersoft
force-pushed
the
keysersoft/playwright-smoke
branch
from
f9d6f72 to
822af41
Compare
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 minimal Playwright suite that boots the frontend on `next dev` and runs three checks:
`webServer` uses `next dev` because `output: 'standalone'` makes `next start` a no-op and the standalone build embeds an absolute path that differs between local and CI.
`.github/workflows/playwright.yml` runs on push and pull_request, installs Chromium with deps, runs the suite, and uploads the report on failure.
Local: 3/3 passed.
Test plan