Repository navigation
Add 2026 sitespeed.io fixtures and guard against dropped metrics - #179
Merged
Merged
Conversation
The old fixture HARs are from 2018 and have no Core Web Vitals, CPU or render-blocking data, so the tests never saw most of what the result page shows. Two recent sitespeed.io tests of the same page, five runs each, now cover those metrics. Cookie values in the HARs are redacted, so no visitor IDs or test-machine location end up in the repository. Metrics are unchanged. A new test renders the result page from these fixtures and fails if any metric we show today disappears, including every CPU category and event. That keeps the coming redesign from silently dropping data. Assisted-by: Claude Opus 5.5 noreply@anthropic.com
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.
The old fixture HARs are from 2018 and have no Core Web Vitals, CPU or render-blocking data, so the tests never saw most of what the result page shows. Two recent sitespeed.io tests of the same page, five runs each, now cover those metrics. Cookie values in the HARs are redacted, so no visitor IDs or test-machine location end up in the repository. Metrics are unchanged.
A new test renders the result page from these fixtures and fails if any metric we show today disappears, including every CPU category and event. That keeps the coming redesign from silently dropping data.
Assisted-by: Claude Opus 5.5 noreply@anthropic.com