e2e-testing_skill

Overview

This skill provides Playwright end-to-end testing and Lighthouse performance auditing for a Rails-based real estate site. It includes setup commands, test patterns, helper utilities, Lighthouse budgets, and CI integration guidance to quickly validate functionality and performance. Use it to run, debug, and automate E2E suites and Lighthouse checks locally or in CI.

How this skill works

It installs Playwright browsers, prepares an e2e Rails environment, and runs tests against two seeded test tenants on port 3001. Tests use shared fixtures and helpers for navigation, auth, form handling, and data reset. Lighthouse CI runs configured audits and asserts against predefined performance and accessibility budgets.

When to use it

• Setting up the E2E environment for the first time
• Running Playwright tests locally or in CI
• Debugging failing E2E tests or flaky behavior
• Re-seeding or resetting test data between runs
• Running Lighthouse performance audits during PRs or on push

Best practices

• Always run npx playwright install once to install browsers before testing
• Seed or reset the e2e database (RAILS_ENV=e2e) before test runs to avoid stale data
• Use the auth-bypass server for admin UI tests to avoid repeated login flows when appropriate
• Group public tests for parallel execution and run admin tests serially to avoid state conflicts
• Capture traces and use the Playwright trace viewer when debugging intermittent failures

Example use cases

• Run the full E2E suite locally: start the e2e server and run npx playwright test
• Iterate on an admin feature: start server_bypass_auth and run only admin project tests
• Verify performance regressions by running npx lhci autorun and reviewing Lighthouse reports
• CI pipeline: reset e2e DB, start bypass-auth server in background, then run Playwright tests
• Re-seed a tenant quickly during development with RAILS_ENV=e2e bin/rails playwright:seed