e2e-user-flows-check

To find missing E2E test coverage, enumerate real user flows from product docs, UI routes, and backend endpoints, then map each candidate to existing Playwright tests to identify uncovered paths. This process highlights untested critical interactions and reduces the risk of shipping broken user journeys.

Mapping backend API endpoints to Playwright E2E tests involves extracting endpoint-driven behaviors as flow candidates and comparing them against existing test definitions. This creates a traceable coverage map that flags backend interactions lacking corresponding UI route or E2E validation.

QA traceability for scenario-based user flows is the process of linking every documented user interaction to a specific E2E test. It ensures every UI route and backend endpoint behavior is verified, producing a prioritized gap report to track untested critical paths.

Prioritize E2E test gaps by auditing observed user flows and categorizing missing test coverage into priority levels from P1 to P4. This ranks untested UI route interactions and backend endpoint behaviors by criticality, guiding QA efforts toward the highest risk areas first.

Yes, you can automatically register missing user flows by appending uncovered candidates to both the USER_FLOW_MAP.md documentation and the flow-definitions.json file. This updates your Playwright E2E test suite with traceable flow candidates that require new test coverage.

E2E user flow auditing can still work without product documentation by relying on repo evidence like UI routes, existing Playwright tests, and backend endpoints to enumerate flows. However, product docs provide crucial scenario context that helps normalize duplicates and identify complete user journeys.