Repository navigation
test(site): Keep recurring event metadata checks focused - #82
Merged
Merged
Conversation
Check representative pairs of recurring events so the date-specific metadata remains covered without loading the entire event calendar in one browser test. This keeps candidate verification within its timeout. Co-authored-by: Codex <noreply@openai.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
Recurring-event metadata remains checked without making the Worker release wait on every event page in one timed browser test.
Overview of Changes
The browser check finds recurring event series from the event index and compares representative pairs. It verifies that each pair shares an event heading and has distinct date-bearing page titles. The check waits for the server-rendered document instead of unrelated network activity.
This fixes the candidate release check that timed out after 900 other browser checks passed.
pnpm checkpassed, and the focused browser test passed locally and against the Worker candidate URL.Follow-ups
None.