Skip to content

fix(e2e): fix flaky rapid-navigation test (stackwright-jh6)#475

Merged
perasperaactual merged 1 commit into
devfrom
fix/stackwright-jh6-flaky-rapid-nav
May 31, 2026
Merged

fix(e2e): fix flaky rapid-navigation test (stackwright-jh6)#475
perasperaactual merged 1 commit into
devfrom
fix/stackwright-jh6-flaky-rapid-nav

Conversation

@perasperaactual
Copy link
Copy Markdown
Contributor

What

Replaces expect(await page.locator('body').innerText()).not.toBe('') with Playwright's auto-retrying await expect(page.locator('main')).toBeVisible() in the rapid navigation loop.

Why

After waitUntil: 'domcontentloaded', client-side React may not have hydrated yet under CI load. The old bare innerText() call has zero retry logic, so it races against hydration and produces a false failure. Playwright's expect(locator) form retries automatically until the configured timeout.

How tested

The fix makes the assertion retry-safe by design. No new test code needed — the change IS the test fix.

Closes bead stackwright-jh6

@github-actions
Copy link
Copy Markdown
Contributor

✅ Visual Regression Test Results

Status: ✅ All visual tests passed!

All screenshots match the baseline. No visual regressions detected! 🎉

@github-actions
Copy link
Copy Markdown
Contributor

⚡ Performance Benchmark Results

✅ Build Time Benchmarks: PASSED

❌ Bundle Size Benchmarks: FAILED

❌ Runtime Vitals Benchmarks: FAILED

📝 Note: Detailed results are available in the job logs.

🎯 Performance Budgets:

  • Build time: <70s total
  • First-load JS: <100KB gzipped
  • FCP: <1.5s, LCP: <2.5s, TTI: <3s

Updated: 2026-05-31T14:13:00.954Z

@perasperaactual perasperaactual merged commit c47f9e9 into dev May 31, 2026
14 of 15 checks passed
@perasperaactual perasperaactual deleted the fix/stackwright-jh6-flaky-rapid-nav branch May 31, 2026 14:13
@github-actions
Copy link
Copy Markdown
Contributor

♿ Accessibility Test Results

Overall Status: ✅ 0/0 tests passed

🦮 WCAG 2.1 AA Compliance

No WCAG test results available

⌨️ Keyboard Navigation

No keyboard navigation test results available


⚠️ No accessibility tests were executed. Check the workflow logs for setup issues.

📊 Detailed Report

Download the full HTML accessibility report from the workflow artifacts for:

  • Detailed WCAG violation descriptions
  • Specific element selectors and fixes
  • Color contrast issues
  • Keyboard navigation flow analysis

🔍 Testing Checklist

Our accessibility tests verify:

  • ✅ WCAG 2.1 Level AA compliance
  • ✅ Color contrast in light and dark modes
  • ✅ Tab key navigation through all interactive elements
  • ✅ Focus indicators are visible
  • ✅ No keyboard traps
  • ✅ Skip links and ARIA landmarks
  • ✅ Screen reader compatibility

Powered by @axe-core/playwright and Playwright

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant