What problem does it solve?
Writing reliable end-to-end tests for the Phoenix web UI requires knowing its page structure, selector conventions, test credentials, and common flakiness pitfalls, which are otherwise scattered across the codebase.
Core Features & Use Cases
- Selector and interaction patterns: Provides prioritized selector guidance (role, label, text, test IDs, CSS) plus patterns for dialogs, tables, tabs, dropdowns, nested submenus, and CodeMirror editors.
- Complete test examples: Includes ready-to-adapt examples for CRUD flows, user management, serial tests with shared state, role-based access control, and playground integration.
- Flakiness debugging guidance: Documents anti-patterns like waitForTimeout, state-based wait strategies, and CI-safe test execution with non-interactive reporters.
- Use Case: When asked to add E2E coverage for a new Phoenix feature, generate a spec file in js/app/tests/ that logs in as admin, navigates to the feature page, and asserts the workflow using stable role selectors.
Quick Start
Write a Playwright test for Phoenix that creates a new dataset and verifies it appears in the datasets table.