webapp-testing

name	webapp-testing
description	Test web applications using Playwright with stable locators, deterministic assertions, trace-first debugging, and defect-oriented reporting.

Webapp Testing

Use this for UI flows, smoke tests, regression tests, flaky browser tests, and validating full-stack behavior from the user perspective.

Workflow

1. Identify the user workflow and critical assertions.
2. Prefer role, label, placeholder, text, and test id locators in that order.
3. Avoid arbitrary waits; wait for stable UI states and network completion only when justified.
4. Validate visible behavior, URL/state changes, console errors, and API side effects where relevant.
5. For failures, capture screenshot, trace, video, console errors, and failed request details.
6. Isolate flakiness before increasing timeout.

Playwright standards

• Use getByRole, getByLabel, getByText, getByTestId.
• Keep tests independent and data-safe.
• Use fixtures for auth/bootstrap when needed.
• Assert user outcomes, not implementation details.
• Prefer API setup/cleanup over slow UI setup when practical.

Output format

• Test objective
• Scenarios covered
• Risks and flake points
• Suggested locators
• Example test structure