new-e2e-test

To scaffold Playwright E2E specs matching existing auth fixtures, provide the app name, route path, flow description, and whether the route is auth-gated. The output is a TypeScript spec file using your project's role-based locators and test conventions.

Flake-resistant Playwright tests use role-based locators instead of brittle CSS selectors and rely on concrete signals rather than fixed waits. Scaffolding new spec files with these conventions ensures stable, consistent E2E test execution across runs.

Yes, Playwright test scaffolding supports unauthenticated public flows for apps like marketing, gen, and rialto-web by applying the standard public @playwright/test pattern instead of auth-gated fixtures.

Auth-gated Playwright tests for a hospitality app should use the repository's existing fixtures.js Auth0 Resource Owner Password Grant approach via environment variables. This ensures secure, automated authentication during E2E test execution.

Avoiding CSS selectors and fixed waits in Playwright E2E testing prevents flakiness caused by DOM changes and timing issues. Using role-based locators and concrete assertion signals creates more resilient and maintainable test specs.