cleanup-e2e-tests

Run the failing spec headlessly, check Cypress screenshots first to see the actual UI state, then classify the error type. Common fixes include updating page object selectors, adding cy.intercept() before triggering actions, and replacing cy.wait(N) with alias-based waits.

Check for hardcoded ports, environment-specific URLs, and timing differences between environments. Fetch CI logs with gh run view, compare screenshots from CI artifacts, and replace fixed waits with network synchronization to eliminate timing sensitivity.

Element not found errors usually mean the test selector no longer matches the actual DOM after a UI change. Compare the selector in the test or page object against the rendered data-* attributes and update the page object rather than individual tests.

No, fixed cy.wait(N) calls cause flaky tests. Instead wait on a cy.intercept() alias like cy.wait('@alias') or assert on a concrete UI condition, so the test proceeds exactly when the application is ready.

Escalate when a failure reveals an architectural issue, such as a genuine application bug, ambiguous product behavior, or a data contract mismatch that mocks cannot resolve. These cases need human decisions rather than test-level patches.