|
2654 | 2654 | "test/development/app-dir/segment-explorer/segment-explorer.test.ts": { |
2655 | 2655 | "passed": [ |
2656 | 2656 | "segment-explorer should cleanup on soft navigation", |
| 2657 | + "segment-explorer should handle show file segments in order", |
2657 | 2658 | "segment-explorer should render the segment explorer for nested routes", |
2658 | 2659 | "segment-explorer should render the segment explorer for parallel routes" |
2659 | 2660 | ], |
|
4075 | 4076 | "flakey": [], |
4076 | 4077 | "runtimeError": false |
4077 | 4078 | }, |
| 4079 | + "test/e2e/app-dir/actions-deployment-skew/actions-deployment-skew.test.ts": { |
| 4080 | + "passed": [ |
| 4081 | + "actions-deployment-skew in the node runtime with a form action and JavaScript disabled should respond with a 404 for an unknown server action", |
| 4082 | + "actions-deployment-skew in the node runtime with a form action and JavaScript enabled should respond with a 404 for an unknown server action", |
| 4083 | + "actions-deployment-skew in the node runtime with a normal action should respond with a 404 for an unknown server action" |
| 4084 | + ], |
| 4085 | + "failed": [], |
| 4086 | + "pending": [ |
| 4087 | + "actions-deployment-skew in the edge runtime with a form action and JavaScript disabled should respond with a 404 for an unknown server action", |
| 4088 | + "actions-deployment-skew in the edge runtime with a form action and JavaScript enabled should respond with a 404 for an unknown server action", |
| 4089 | + "actions-deployment-skew in the edge runtime with a normal action should respond with a 404 for an unknown server action" |
| 4090 | + ], |
| 4091 | + "flakey": [], |
| 4092 | + "runtimeError": false |
| 4093 | + }, |
4078 | 4094 | "test/e2e/app-dir/actions-navigation/index.test.ts": { |
4079 | 4095 | "passed": [ |
4080 | 4096 | "app-dir action handling should handle actions correctly after following a relative link", |
|
4158 | 4174 | "app-dir action handling fetch actions should store revalidation data in the prefetch cache", |
4159 | 4175 | "app-dir action handling redirects displays searchParams correctly when redirecting with SearchParams", |
4160 | 4176 | "app-dir action handling redirects merges cookies correctly when redirecting", |
4161 | | - "app-dir action handling redirects redirects properly when server action handler redirects with a 307 status code", |
4162 | | - "app-dir action handling redirects redirects properly when server action handler redirects with a 308 status code", |
| 4177 | + "app-dir action handling redirects redirects properly when route handler redirects with a 307 status code", |
| 4178 | + "app-dir action handling redirects redirects properly when route handler redirects with a 308 status code", |
4163 | 4179 | "app-dir action handling redirects redirects properly when server action handler uses `permanentRedirect`", |
4164 | 4180 | "app-dir action handling redirects redirects properly when server action handler uses `redirect`", |
4165 | 4181 | "app-dir action handling redirects should not forward next-action header to a redirected RSC request", |
|
4288 | 4304 | "app-dir action handling fetch actions should store revalidation data in the prefetch cache", |
4289 | 4305 | "app-dir action handling redirects displays searchParams correctly when redirecting with SearchParams", |
4290 | 4306 | "app-dir action handling redirects merges cookies correctly when redirecting", |
4291 | | - "app-dir action handling redirects redirects properly when server action handler redirects with a 307 status code", |
4292 | | - "app-dir action handling redirects redirects properly when server action handler redirects with a 308 status code", |
| 4307 | + "app-dir action handling redirects redirects properly when route handler redirects with a 307 status code", |
| 4308 | + "app-dir action handling redirects redirects properly when route handler redirects with a 308 status code", |
4293 | 4309 | "app-dir action handling redirects redirects properly when server action handler uses `permanentRedirect`", |
4294 | 4310 | "app-dir action handling redirects redirects properly when server action handler uses `redirect`", |
4295 | 4311 | "app-dir action handling redirects should not forward next-action header to a redirected RSC request", |
|
6289 | 6305 | }, |
6290 | 6306 | "test/e2e/app-dir/fallback-shells/fallback-shells.test.ts": { |
6291 | 6307 | "passed": [ |
6292 | | - "fallback-shells with cached IO and the page not wrapped in Suspense and params.then/catch/finally passed to a cached function does not resume a postponed fallback shell", |
6293 | | - "fallback-shells with cached IO and the page not wrapped in Suspense and the params accessed in a cached non-page function does not resume a postponed fallback shell", |
6294 | | - "fallback-shells with cached IO and the page not wrapped in Suspense and the params accessed in the cached page does not render a fallback shell when using a params placeholder", |
6295 | | - "fallback-shells with cached IO and the page not wrapped in Suspense and the params accessed in the cached page does not resume a postponed fallback shell", |
6296 | | - "fallback-shells with cached IO and the page wrapped in Suspense and params.then/catch/finally passed to a cached function resumes a postponed fallback shell", |
6297 | | - "fallback-shells with cached IO and the page wrapped in Suspense and the params accessed in cached non-page function resumes a postponed fallback shell", |
6298 | | - "fallback-shells with cached IO and the page wrapped in Suspense and the params accessed in the cached page resumes a postponed fallback shell", |
6299 | | - "fallback-shells with cached IO and the page wrapped in Suspense and the params accessed in the cached page shares a cached parent layout between a prerendered route shell and the fallback shell", |
| 6308 | + "fallback-shells with cached IO with generateStaticParams and the page not wrapped in Suspense and params.then/catch/finally passed to a cached function does not resume a postponed fallback shell", |
| 6309 | + "fallback-shells with cached IO with generateStaticParams and the page not wrapped in Suspense and the params accessed in a cached non-page function does not resume a postponed fallback shell", |
| 6310 | + "fallback-shells with cached IO with generateStaticParams and the page not wrapped in Suspense and the params accessed in the cached page does not render a fallback shell when using a params placeholder", |
| 6311 | + "fallback-shells with cached IO with generateStaticParams and the page not wrapped in Suspense and the params accessed in the cached page does not resume a postponed fallback shell", |
| 6312 | + "fallback-shells with cached IO with generateStaticParams and the page not wrapped in Suspense and the params transformed with an async function and then passed to a cached function does not resume a postponed fallback shell", |
| 6313 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and params.then/catch/finally passed to a cached function resumes a postponed fallback shell", |
| 6314 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and the params accessed in cached non-page function resumes a postponed fallback shell", |
| 6315 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and the params accessed in the cached page does not produce hydration errors when resuming a fallback shell containing a layout with unused params", |
| 6316 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and the params accessed in the cached page resumes a postponed fallback shell", |
| 6317 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and the params accessed in the cached page shares a cached parent layout between a prerendered route shell and the fallback shell", |
| 6318 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and the params transformed with an async function and then passed to a cached function resumes a postponed fallback shell", |
| 6319 | + "fallback-shells with cached IO without generateStaticParams and params.then/catch/finally passed to a cached function resumes a postponed fallback shell", |
| 6320 | + "fallback-shells with cached IO without generateStaticParams and the params accessed in cached non-page function resumes a postponed fallback shell", |
| 6321 | + "fallback-shells with cached IO without generateStaticParams and the params accessed in the cached page resumes a postponed fallback shell", |
6300 | 6322 | "fallback-shells without IO should start and not postpone the response" |
6301 | 6323 | ], |
6302 | 6324 | "failed": [], |
6303 | 6325 | "pending": [ |
6304 | | - "fallback-shells with cached IO and the page wrapped in Suspense and the params accessed in the cached page does not produce hydration errors when resuming a fallback shell containing a layout with unused params", |
6305 | | - "fallback-shells with cached IO and the page wrapped in Suspense and the params accessed in the cached page shares a cached layout with unused params between a prerendered route shell and the fallback shell" |
| 6326 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and the params accessed in the cached page includes a cached layout with unused params in the fallback shell", |
| 6327 | + "fallback-shells with cached IO with generateStaticParams and the page wrapped in Suspense and the params accessed in the cached page shares a cached layout with unused params between a prerendered route shell and the fallback shell", |
| 6328 | + "fallback-shells with cached IO without generateStaticParams and the params accessed in the cached page does not produce hydration errors when resuming a fallback shell containing a layout with unused params", |
| 6329 | + "fallback-shells with cached IO without generateStaticParams and the params accessed in the cached page includes a cached layout with unused params in the fallback shell" |
6306 | 6330 | ], |
6307 | 6331 | "flakey": [], |
6308 | 6332 | "runtimeError": false |
|
6964 | 6988 | "app-dir - metadata-streaming should still load viewport meta tags even if metadata is delayed", |
6965 | 6989 | "app-dir - metadata-streaming static should determine dynamic metadata in build and render in the body", |
6966 | 6990 | "app-dir - metadata-streaming static should render static metadata in the head", |
| 6991 | + "app-dir - metadata-streaming static should still render blocking metadata for Google speed insights bot (special case)", |
6967 | 6992 | "app-dir - metadata-streaming static should still render dynamic metadata in the head for html bots" |
6968 | 6993 | ], |
6969 | 6994 | "failed": [], |
|
0 commit comments