webapp-testinglisted

Test the application in a real browser rather than claiming it works from a code read alone. A passing type-check or unit test does not mean the page renders, the form submits, or the network request succeeds. Run the app, drive it with Playwright, and report what actually happened. ## Step 1: Check for Playwright and a running app ```bash # Check if Playwright is installed npx playwright --version 2>/dev/null || echo "not installed" # Check if there is an existing Playwright config ls playwright.config.ts playwright.config.js 2>/dev/null ``` If Playwright is not installed, install it: ```bash npm install --save-dev @playwright/test npx playwright install chromium ``` Check whether the dev server is already running. If not, start it before writing tests. Use the project's start script - check `package.json` for the correct command (`npm run dev`, `npm start`, etc.). The server must be running for Playwright to connect. ## Step 2: Identify what to verify Before writing any test, state the scenario in plain terms: - What page or URL does the scenario start from? - What actions does the user take? (navigate, click, type, submit, wait) - What is the expected outcome? (page title changes, element appears, URL changes, form resets, API call completes) - Are there any states to verify along the way? (loading indicator, validation message, success confirmation) If the user has not specified a scenario, default to: navigate to the app's root, confirm it loads without console