Several Playwright assertions in packages/kit/test/apps/basics/test/client.test.js use web-first matchers without awaiting them, so the returned promise floats and the assertion never actually runs. The affected tests pass regardless of the real page URL or text content, which means they provide no coverage today.

Affected assertions:

• expect(page).toHaveURL(...) in "data-sveltekit-preload-data network failure does not trigger navigation" (sole assertion of the test).
• two expect(page).toHaveURL(...) calls in "data-sveltekit-preload-data error does not block user navigation" (the only assertions of the test).
• expect(page).toHaveURL(...) in "data-sveltekit-preload does not abort ongoing navigation" (sole assertion).
• expect(page).toHaveURL(...) in "data-sveltekit-preload does not abort ongoing navigation add create-svelte package #2".
• expect(await page.locator('h2')).toHaveText(...) in "uses correct dynamic env when navigating from prerendered page". Here the await is on the locator (a no-op) rather than on the assertion, so the matcher still floats. Sole assertion of the test.

The fix adds the missing await (and moves it outside expect() for the h2 case) so each matcher runs and can fail. No test titles, selectors, or expected values are changed; this only makes the existing assertions effective.

Tests

• I was not able to run the full Playwright e2e suite locally (the demo apps require a build/dev server in my environment). The change is a mechanical addition of missing awaits to existing assertions, with no behavior, selector, or expected-value change.

Changesets

• No changeset: this is a test-only change under packages/kit/test/ with no published-package changelog impact.

Edits

• Allow edits from maintainers is enabled.

Found while reviewing the test suite with e2e-skills/e2e-reviewer.