Skip to content

Conversation

@PABannier
Copy link
Owner

@PABannier PABannier commented Jan 22, 2026

Summary

  • Remove E2E tests entirely - they provided marginal value over existing unit/integration tests
  • E2E tests were slow (37 min), flaky, and mostly redundant with:
    • useSession.test.ts (26 tests)
    • useWebSocket.test.ts (14 tests)
    • usePresence.test.ts (14 tests)
    • Backend performance tests (bench_smoke, bench_standard)

What was removed

  • web/e2e/ directory (all Playwright test files)
  • web/playwright.config.ts
  • E2E-related scripts from package.json
  • @playwright/test dependency
  • e2e-tests job from CI workflow

Impact

  • CI will be faster (no 37 min E2E job)
  • 117 unit tests still provide comprehensive coverage
  • Backend perf tests still validate real HTTP/WS integration

🤖 Generated with Claude Code

PABannier and others added 2 commits January 22, 2026 22:45
In Playwright, timing() is a method on the Request object, not the
Response object. This was causing all E2E tests to fail with
"TypeError: res.timing is not a function".

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The E2E tests provided marginal value:
- Mostly redundant with existing unit tests (useSession, useWebSocket, etc.)
- Slow (37 min) and flaky due to timing dependencies
- Backend perf tests already cover real HTTP/WS integration
- No unique coverage that unit/integration tests don't already provide

This removes:
- web/e2e/ directory (all Playwright test files)
- web/playwright.config.ts
- E2E-related scripts from package.json
- @playwright/test dependency
- e2e-tests job from CI workflow

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@PABannier PABannier changed the title fix: use correct Playwright API for response timing in E2E tests chore: remove E2E tests in favor of unit and integration tests Jan 22, 2026
@PABannier PABannier merged commit 1edc3be into main Jan 22, 2026
3 checks passed
@PABannier PABannier deleted the fix/e2e-playwright-timing-api branch January 22, 2026 21:59
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.

2 participants