Repository navigation
test(e2e): pin a11y dashboard pages to the fixture date range - #148
Conversation
The fixture data is fixed at 2026-09-28..30. With the default rolling period the dashboard lost it once those days left the window, so the world map never rendered and the a11y audit failed.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Set date range on test routes web/e2e/a11y-audit.spec.ts |
The audit, skip-link test, and breakpoint screenshot test now include the fixed date range in their dashboard and sessions routes. |
Possibly related PRs
- velixio/supermetry#145: Keeps fixture sites outside the retention window for the same 28–30 September 2026 fixture period.
Merge Risk: 
Minimal · up to 013fc
-
This test-only change aligns accessibility routes with the available fixture dates and is ready to merge.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files.
-
The a11y audit opened the dashboard with the default rolling period. The e2e fixture data is fixed at 2026-09-28..30, so once those days left the window the Where card had no countries, the world map never rendered, and three a11y tests failed (seen on #146). The dashboard and sessions pages now use the same fixed custom range as the other dashboard specs.
Verified locally: without the change the skip-link test fails with the same world-map locator error as CI, and with it all 4 a11y tests pass.