Skip to content

test(checker): Google-shaped feed records time moves and fans them out - #21

Merged
Wjouter merged 1 commit into
mainfrom
test/google-feed-time-moves
Nov 11, 2026
Merged

Wjouter merged 1 commit into
mainfrom
test/google-feed-time-moves

Conversation

@Wjouter

@Wjouter Wjouter commented Oct 25, 2026

Copy link
Copy Markdown
Owner

Why

A missed time change on a Google calendar in production (v0.1.1) wasn't a bug. A read-only check on the server showed the calendar is ok and checked every 10 minutes, but the feed Google serves still has the old times (the newest LAST-MODIFIED is 30 Sept). Google's iCal feed is slow to update. Still, no test fixture had Google's shape, so this adds one.

What

  • Fixtures/google.ics / google-edited.ics: a synthetic feed in Google's format (X-WR-TIMEZONE:Europe/Brussels, an all-day VALUE=DATE event, UTC Z times, a weekly series).
  • CheckerTests.GoogleFeedTimeMovesAreRecordedAndFannedOut: moves the single event, the all-day event and one occurrence of the series (a RECURRENCE-ID override, i.e. "this event only"). It asserts one changed/time row each, the exact old and new times for the single event, and one pending delivery per change.

Test only; no production code changes.

Tests

Full backend suite: 475 passed, 6 skipped.

🤖 Generated with Claude Code

A report of missed time changes on a Google calendar turned out to be
Google serving a stale feed, but no fixture had Google's shape: all-day
VALUE=DATE events, UTC times and a "this event only" RECURRENCE-ID
override. The new test moves one of each and asserts a changed/time row
per event and a pending delivery per change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Wjouter
Wjouter merged commit 65815ba into main Nov 11, 2026
6 checks passed
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