debug-failed-integration-test

Debug failing Playwright E2E tests by reproducing the exact spec locally against the real backend, then correlating frontend test output with Spring Boot state-change logs to pinpoint the precise rejection or stalled phase before applying fixes.

Fix flaky integration tests on GitHub Actions by using an evidence-driven approach: reproduce the failing spec locally, inspect backend and frontend logs, apply a DOM-first fix using testids, and verify the result across multiple stable runs without relying on timeouts or retries.

Playwright specs failing on pull requests require matching frontend output with Spring Boot logs to identify the exact failure. Handle quarantined specs by reproducing them locally against the real backend and applying product-code corrections rather than guesswork.

Yes, DOM-first fixes resolve E2E test failures by preferring testids, real user interactions, and product-code corrections over timeouts, retries, or guesswork, ensuring the underlying bug is addressed rather than masked by unstable test behavior.

Verify a Playwright test fix before merging by confirming repeated stable runs, type checks, unit tests, and monitored PR checks on GitHub Actions, ensuring the red build turns green through evidence-backed root cause resolution rather than intermittent passes.

When a Playwright shard turns red on a GitHub Actions pull request, re-run the exact failing spec locally against the real backend, inspect both Spring Boot and Playwright logs to correlate failures, and apply a targeted DOM-first fix followed by CI verification.