rule-frontend-e2e-tests

What problem does it solve?

This rule enforces standardized tagging and organization for Playwright E2E tests in the frontend/tests/e2e directory, ensuring consistency across the team.

Core Features & Use Cases

• Execution tagging: Each test must have exactly one execution tag (e.g., @smoke, @core-regression, @full-regression, @extended) to control CI runs.
• Optional feature tags: Use centralized feature tags (e.g., @grantee, @opportunity-search, @apply) defined in frontend/tests/e2e/tags.ts to classify tests.
• Directory and naming conventions: Organize tests by feature under frontend/tests/e2e and name files consistently (happy-path vs failure-path patterns where applicable).
• Page object utilities: Prefer utility-based page objects and place feature utilities under frontend/tests/e2e/utils.
• Test data and fixtures: Use dedicated fixtures and utilities; avoid embedding large data inline in specs.
• Playwright configuration awareness: Follow environment-specific timeouts, retries, and reporting guidance to ensure reliable test runs.
• BDD feature files: .feature files may accompany .spec.ts files; leverage Gherkin for scenario definitions when appropriate.

Quick Start

Tag each E2E test with exactly one execution tag and organize tests under feature folders in frontend/tests/e2e.