Skip to content

test(web): stabilize week registry clock#1810

Closed
Uarmagan wants to merge 1 commit into
mainfrom
fix/week-event-registry-date-drift
Closed

test(web): stabilize week registry clock#1810
Uarmagan wants to merge 1 commit into
mainfrom
fix/week-event-registry-date-drift

Conversation

@Uarmagan
Copy link
Copy Markdown
Contributor

Summary

  • Freeze the Week event registry test clock so its May 2026 past/future examples stay stable.
  • Restore real time after each test.

Evidence

  • GitHub Actions Test run 26301965222 failed in unit (web), job 77429129727, at packages/web/src/views/Week/interaction/registry/weekEventRegistry.test.tsx:411.
  • Local reproduction on ac02269 failed the same test because the event ending 2026-05-22 was treated as past on 2026-05-23.

Verification

  • bun test --cwd packages/web src/views/Week/interaction/registry/weekEventRegistry.test.tsx
  • bun test:web
  • bun type-check
  • bun lint

@tyler-dane
Copy link
Copy Markdown
Contributor

Closed in favor of #1812. Changing the system time is a smell that the app code / test logic is brittle

@tyler-dane tyler-dane closed this May 24, 2026
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