Skip to content

Update Turbopack development test manifest #80744

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

Closed

Conversation

vercel-release-bot
Copy link
Contributor

This auto-generated PR updates the development integration test manifest used when testing Turbopack.

@ijjk ijjk added CI approved Approve running CI for fork tests labels Jun 21, 2025
@ijjk
Copy link
Member

ijjk commented Jun 21, 2025

Failing test suites

Commit: 286d2ff

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/e2e/app-dir/navigation/navigation.test.ts (PPR)

  • app dir - navigation > middleware redirect > should change browser location when router.refresh() gets a redirect response
Expand output

● app dir - navigation › middleware redirect › should change browser location when router.refresh() gets a redirect response

expect(received).toBe(expected) // Object.is equality

Expected: "http://localhost:35957/redirect-on-refresh/dashboard"
Received: "http://localhost:35957/redirect-on-refresh/auth"

  984 |       const browser = await next.browser('/redirect-on-refresh/auth')
  985 |       await retry(async () =>
> 986 |         expect(await browser.url()).toBe(
      |                                     ^
  987 |           next.url + '/redirect-on-refresh/dashboard'
  988 |         )
  989 |       )

  at toBe (e2e/app-dir/navigation/navigation.test.ts:986:37)
  at retry (lib/next-test-utils.ts:811:14)
  at Object.<anonymous> (e2e/app-dir/navigation/navigation.test.ts:985:7)

Read more about building and testing Next.js in contributing.md.

pnpm test-dev test/e2e/app-dir/actions/app-action.test.ts

  • app-dir action handling > fetch actions > should handle redirects to routes that provide an invalid RSC response
Expand output

● app-dir action handling › fetch actions › should handle redirects to routes that provide an invalid RSC response

expect(received).toContain(expected) // indexOf

Expected substring: "Hello from a pages route"
Received string:    "0.5971372774824242
Client
Server
Client and Server
0
+1+1 (Slow)-1*2
redirect to a pages route
submit
test"

  1315 |
  1316 |       await retry(async () => {
> 1317 |         expect(await browser.elementByCss('body').text()).toContain(
       |                                                           ^
  1318 |           'Hello from a pages route'
  1319 |         )
  1320 |         expect(await browser.url()).toBe(`${next.url}/pages-dir`)

  at toContain (e2e/app-dir/actions/app-action.test.ts:1317:59)
  at retry (lib/next-test-utils.ts:811:14)
  at Object.<anonymous> (e2e/app-dir/actions/app-action.test.ts:1316:7)

Read more about building and testing Next.js in contributing.md.

@github-actions github-actions bot added the locked label Jul 6, 2025
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants