0036-laravel-e2e-playwright

Laravel Playwright E2E tests become flaky due to inconsistent state setup, fragile CSS selectors, and UI-based authentication. You fix this by using migrate:fresh --seed, data-testid attributes, and API-based authentication.

You establish environment consistency for Laravel Playwright testing by using a dedicated .env.playwright file and rebuilding the database schema reliably with migrate:fresh --seed before running your tests.

The best way to handle authentication in Playwright for Laravel is reusing Playwright storage state or creating users via API/setup, which avoids UI login flakiness and ensures deterministic login handling across specs.

You manage database state between Playwright test specs by adding seeders for common scenarios and using model factories for per-test setup while resetting the database state between each specification.

Yes, this Playwright Laravel testing setup works with Sail and non-Sail environments, supporting deterministic login handling and state setup across both configurations using sail pnpm playwright:test.

You reduce slow execution and diagnose failures in Playwright E2E tests by asserting key milestones, splitting large flows into steps, and recording videos or screenshots only on failure to reduce overhead.