Problem: After waitForAngular, content assertions ran before Angular's
XHR data loaded. Tests checked textContent('body') at a point when
the table/heading hadn't rendered yet.
Fix: Replace point-in-time checks with Playwright auto-retry assertions:
- expect(locator).toBeVisible({ timeout: 15_000 }) — retries until visible
- expect(locator).toContainText('X', { timeout: 15_000 }) — retries until text appears
- expect(rows.first()).toBeVisible() — retries until table has data
Also: landing page test now uses waitForFunction to detect Angular redirect.
10 files changed, net -45 lines (simpler, more robust assertions).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The 3s waitForTimeout after page.goto wasn't enough for Angular to
bootstrap and render content. Replace with waitForAngular() helper
that waits for actual DOM elements (nav, headings) up to 15s, with
5s fallback.
32 calls updated across 10 test files.
Also adds waitForAngular to helpers.ts export.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Three fixes resolving the cascading test failures:
1. Add withRetry() to integrations.e2e.spec.ts advisory section — the
6 API tests that 504'd on Concelier transport now retry up to 2x
2. Change all UI test page.goto from networkidle to domcontentloaded
across 9 test files — networkidle never fires when Angular XHR
calls 504, causing 30 UI tests to timeout. domcontentloaded fires
when HTML is parsed, then 3s wait lets Angular render.
3. Fix test dependencies — vault-consul-secrets detail test now creates
its own integration instead of depending on prior test state.
New test: catalog page aggregation report — verifies the advisory
source catalog page shows stats bar metrics and per-source freshness
data (the UI we built earlier this session).
Files changed: integrations.e2e.spec.ts, vault-consul-secrets, ui-*,
runtime-hosts, gitlab-integration, error-resilience, aaa-advisory-sync
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
