Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add full-page navigation e2e tests #63268

Draft
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

michalczaplinski
Copy link
Contributor

@michalczaplinski michalczaplinski commented Jul 8, 2024

What?

Add new e2e tests for full-page navigation using the Interactivity API.

Why?

To ensure that the full-page client-side navigation feature is stable. The goal is to implement the tests mentioned in #59707 (comment)

  • A site becomes interactive without adding interactive blocks.
  • Internal links navigate without reloading the page.
  • External links navigate reloading the page.
  • State/context is preserved/updated during navigation
  • All cases from the router-navigate spec file should work with the experiment enabled.

I also simply wanted to create a base of a few tests for full-page navigation that can then be re-used when implementing the asset loading strategy for full-page navigations.

Add a new e2e test for full-page navigation. The test ensures that the `<head>` element is preserved during navigation between pages.
@michalczaplinski michalczaplinski added [Type] Code Quality Issues or PRs that relate to code quality [Package] E2E Tests /packages/e2e-tests [Feature] Interactivity API API to add frontend interactivity to blocks. labels Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Interactivity API API to add frontend interactivity to blocks. [Package] E2E Tests /packages/e2e-tests [Type] Code Quality Issues or PRs that relate to code quality
1 participant