🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Adding Playwright E2E testing to the developer workflow in order to catch regressions in browsers before they land in the stable channels of major browsers.

E2E Test TODOS

• Install and configure Playwright
• Add ability to launch and wait for internal server endpoint to return success code
• Write a smoke test with Playwright E2E
• Add a11y improvements to home page to be able to locate elements without coupling to DOM structure
• Create a GHA to run Playwright in CI on PRs
• Add package.json task to execute E2E tests locally (currently pnpm playwright test)

Cross-browser Test TODOS

Can be split out into its own PR. Adding Playwright without comprehensive cross-browser testing will still catch Chromium issues.

• Set up SauceLabs to add cross-browser support for the smoke test
• Add SauceLabs actions (Sauce Connect)
• Add video to this PR and instructions to README/CONTRIBUTING file
• Add package.json task to execute Sauce Labs-enabled E2E tests locally
• Add .env.local details to document required environment variables
• Create weekly/nightly Sauce Labs job to target Dev and Beta Chrome channels
• Cut over credentials to Anthony/Nuxt Core team