Summary
The Navigation Timing API log emits four fields on each page load but has no unit tests verifying the field values are correctly extracted from the PerformanceNavigationTiming entry. Tests should confirm each field is a non-negative number and that the log is not emitted when timing data is unavailable.
Scope
- Mock a
PerformanceNavigationTiming entry with known values
- Assert the emitted log contains
dom_content_loaded_ms, load_event_ms, time_to_first_byte_ms, and route
- Assert all timing fields are non-negative numbers
- Mock the case where
PerformanceNavigationTiming is unavailable and assert no log is emitted
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram
Summary
The Navigation Timing API log emits four fields on each page load but has no unit tests verifying the field values are correctly extracted from the
PerformanceNavigationTimingentry. Tests should confirm each field is a non-negative number and that the log is not emitted when timing data is unavailable.Scope
PerformanceNavigationTimingentry with known valuesdom_content_loaded_ms,load_event_ms,time_to_first_byte_ms, androutePerformanceNavigationTimingis unavailable and assert no log is emittedAcceptance Criteria
routematches the current route stringETA: 12 hours
Coordinate on Telegram