Browser/E2E, Playwright, and Allure
Boundary
Section titled “Boundary”Browser/E2E testing is post-deployment. It is not the source CI gate for nexa-web or nexa-backend; Vitest remains that gate.
Current and target state
Section titled “Current and target state”nexa-web currently includes custom .mjs browser flows in recent work. These may continue while the suite is migrated and rationalized. The target maintained standard is Playwright running against stable Dev/Test URLs with Allure as the detailed execution-history and evidence layer.
Required practices
Section titled “Required practices”- Cover a small set of critical user journeys and cross-service workflows.
- Use least-privilege test accounts and controlled test data.
- Centralize selectors, authentication setup, and reusable fixtures.
- Capture traces, screenshots, videos, console output, and network diagnostics on failure.
- Keep browser tests independent and safe to retry.
- Quarantine is time-boxed; flaky tests must have an owner and remediation date.
Reporting boundaries
Section titled “Reporting boundaries”- SonarQube: static analysis and source-unit coverage imported from Vitest/Pytest.
- Allure: deployed browser, API, contract, and integration execution history.
- GitHub Actions: workflow result and artifact links.
No single tool is presented as the source of truth for every quality signal.