Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Add SPA user journey tests for soft navigations - #2561

#2561
Open
soulgalore wants to merge 2 commits into
mainsitespeedio/browsertime:mainfrom
spa-user-journeyssitespeedio/browsertime:spa-user-journeysCopy head branch name to clipboard
Open

Add SPA user journey tests for soft navigations#2561
soulgalore wants to merge 2 commits into
mainsitespeedio/browsertime:mainfrom
spa-user-journeyssitespeedio/browsertime:spa-user-journeysCopy head branch name to clipboard

Conversation

@soulgalore

Copy link
Copy Markdown
Member

Browsertime recently learned to measure SPA soft navigations, including ones that never touch the network, but the CI coverage was two single-step scripts. Real SPA sessions are multi-step journeys that mix routes with requests, routes rendered entirely from memory, and the occasional full page load, and regressions in the HAR page pairing or the per-step soft navigation slicing only show up in those flows.

This turns the SPA test page into a small multi-route app and adds three user journeys: one covering fetch, no-request and image routes, one mixing soft and hard navigations, and one with only zero-request navigations. The journeys wait with the page complete check instead of fixed sleeps, so they also exercise the SPA inactivity logic they are meant to protect. Firefox runs the multi-route journey too, asserting that journeys complete in browsers without the soft navigation API.

Co-authored-by: Claude Fable 5 noreply@anthropic.com
Change-Id: I81333ebc8478f6930d8dc906d839822e69e75c38

Browsertime recently learned to measure SPA soft navigations, including ones that never touch the network, but the CI coverage was two single-step scripts. Real SPA sessions are multi-step journeys that mix routes with requests, routes rendered entirely from memory, and the occasional full page load, and regressions in the HAR page pairing or the per-step soft navigation slicing only show up in those flows.

This turns the SPA test page into a small multi-route app and adds three user journeys: one covering fetch, no-request and image routes, one mixing soft and hard navigations, and one with only zero-request navigations. The journeys wait with the page complete check instead of fixed sleeps, so they also exercise the SPA inactivity logic they are meant to protect. Firefox runs the multi-route journey too, asserting that journeys complete in browsers without the soft navigation API.

Co-authored-by: Claude Fable 5 noreply@anthropic.com
Change-Id: I81333ebc8478f6930d8dc906d839822e69e75c38
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

Morty Proxy This is a proxified and sanitized view of the page, visit original site.