{
"test/development/acceptance-app/ReactRefresh.test.ts": {
"passed": [
"ReactRefresh app can edit a component without losing state",
"ReactRefresh app cyclic dependencies"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshLogBox-builtins.test.ts": {
"passed": [
"ReactRefreshLogBox-builtins app Module not found",
"ReactRefreshLogBox-builtins app Module not found empty import trace",
"ReactRefreshLogBox-builtins app Module not found missing global CSS",
"ReactRefreshLogBox-builtins app Node.js builtins"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshLogBox-scss.test.ts": {
"passed": [],
"failed": [],
"pending": [
"ReactRefreshLogBox scss app scss module pure selector error",
"ReactRefreshLogBox scss app scss syntax errors"
],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshLogBox.test.ts": {
"passed": [
"ReactRefreshLogBox app Call stack for client error",
"ReactRefreshLogBox app Call stack for server error",
"ReactRefreshLogBox app Can't resolve @import in CSS file",
"ReactRefreshLogBox app Import trace when module not found in layout",
"ReactRefreshLogBox app Server component errors should open up in fullscreen",
"ReactRefreshLogBox app Should not show __webpack_exports__ when exporting anonymous arrow function",
"ReactRefreshLogBox app Should show error location for server actions in client component",
"ReactRefreshLogBox app Should show error location for server actions in server component",
"ReactRefreshLogBox app Unhandled errors and rejections opens up in the minimized state",
"ReactRefreshLogBox app boundaries",
"ReactRefreshLogBox app conversion to class component (1)",
"ReactRefreshLogBox app css syntax errors",
"ReactRefreshLogBox app logbox: anchors links in error messages",
"ReactRefreshLogBox app module init error not shown",
"ReactRefreshLogBox app server component can recover from error thrown in the module",
"ReactRefreshLogBox app should collapse bundler internal stack frames",
"ReactRefreshLogBox app should hide unrelated frames in stack trace with nodejs internal calls",
"ReactRefreshLogBox app should hide unrelated frames in stack trace with unknown anonymous calls",
"ReactRefreshLogBox app should strip whitespace correctly with newline",
"ReactRefreshLogBox app unterminated JSX"
],
"failed": [],
"pending": [
"ReactRefreshLogBox app internal package errors",
"ReactRefreshLogBox app non-Error errors are handled properly"
],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshLogBoxMisc.test.ts": {
"passed": ["ReactRefreshLogBox app server-side only compilation errors"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshModule.test.ts": {
"passed": ["ReactRefreshModule app should allow any variable names"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshRegression.test.ts": {
"passed": [
"ReactRefreshRegression app can fast refresh a page with config",
"ReactRefreshRegression app can fast refresh a page with dynamic rendering",
"ReactRefreshRegression app can fast refresh a page with static generation",
"ReactRefreshRegression app custom loader mdx should have Fast Refresh enabled",
"ReactRefreshRegression app shows an overlay for anonymous function server-side error",
"ReactRefreshRegression app shows an overlay for server-side error in client component",
"ReactRefreshRegression app shows an overlay for server-side error in server component"
],
"failed": [],
"pending": [
"ReactRefreshRegression app styled-components hydration mismatch"
],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshRequire.test.ts": {
"passed": [
"ReactRefreshRequire app bails out if the update bubbles to the root via one of the paths",
"ReactRefreshRequire app bails out if update bubbles to the root via the only path",
"ReactRefreshRequire app can continue hot updates after module-level errors with ES6 exports",
"ReactRefreshRequire app can continue hot updates after module-level errors with module.exports",
"ReactRefreshRequire app can replace a module before it is loaded",
"ReactRefreshRequire app does not accumulate stale exports over time",
"ReactRefreshRequire app propagates a hot update to closest accepted module",
"ReactRefreshRequire app propagates hot update to all inverse dependencies",
"ReactRefreshRequire app provides fresh value for ES6 default import in parents",
"ReactRefreshRequire app provides fresh value for ES6 named import in parents",
"ReactRefreshRequire app provides fresh value for exports.* in parents",
"ReactRefreshRequire app provides fresh value for module.exports in parents",
"ReactRefreshRequire app re-runs accepted modules",
"ReactRefreshRequire app runs dependencies before dependents",
"ReactRefreshRequire app stops update propagation after module-level errors"
],
"failed": [],
"pending": [
"ReactRefreshRequire app propagates a module that stops accepting in next version"
],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/app-hmr-changes.test.ts": {
"passed": [],
"failed": [],
"pending": [
"Error overlay - RSC build errors Skipped in webpack should handle successive HMR changes with errors correctly"
],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/dynamic-metadata-error.test.ts": {
"passed": [
"dynamic metadata error should error if the default export of dynamic image is missing",
"dynamic metadata error should error when id is missing in generateImageMetadata",
"dynamic metadata error should error when id is missing in generateSitemaps"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/editor-links.test.ts": {
"passed": [
"Error overlay - editor links opening links in import traces should be possible to open import trace files on RSC parse error",
"Error overlay - editor links should be possible to open source file on build error"
],
"failed": [
"Error overlay - editor links opening links in import traces should be possible to open import trace files on module not found error"
],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/error-message-url.test.ts": {
"passed": [
"Error overlay - error message urls should be possible to click url in build error",
"Error overlay - error message urls should be possible to click url in runtime error"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/error-recovery.test.ts": {
"passed": [
"Error recovery app can recover from a event handler error",
"Error recovery app client component can recover from a component error",
"Error recovery app client component can recover from syntax error",
"Error recovery app displays build error on initial page load",
"Error recovery app render error not shown right after syntax error",
"Error recovery app server component can recover from a component error",
"Error recovery app server component can recover from syntax error",
"Error recovery app stuck error",
"Error recovery app syntax > runtime error"
],
"failed": [
"Error recovery app can recover from a syntax error without losing state"
],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/hydration-error.test.ts": {
"passed": [
"Error overlay for hydration errors in App router includes a React docs link when hydration error does occur",
"Error overlay for hydration errors in App router should not show a hydration error when using `useId` in a client component",
"Error overlay for hydration errors in App router should only show one hydration error when bad nesting happened - div > tr",
"Error overlay for hydration errors in App router should only show one hydration error when bad nesting happened - div under p",
"Error overlay for hydration errors in App router should only show one hydration error when bad nesting happened - p under p",
"Error overlay for hydration errors in App router should show correct hydration error when client and server render different text",
"Error overlay for hydration errors in App router should show correct hydration error when client renders an extra element",
"Error overlay for hydration errors in App router should show correct hydration error when client renders an extra node inside Suspense content",
"Error overlay for hydration errors in App router should show correct hydration error when client renders an extra text node",
"Error overlay for hydration errors in App router should show correct hydration error when extra attributes set on server",
"Error overlay for hydration errors in App router should show correct hydration error when server renders an extra element",
"Error overlay for hydration errors in App router should show correct hydration error when server renders an extra text node",
"Error overlay for hydration errors in App router should show correct hydration error when server renders an extra text node in an invalid place",
"Error overlay for hydration errors in App router should show correct hydration error when server renders an extra whitespace in an invalid place",
"Error overlay for hydration errors in App router should show error if script is directly placed under html instead of body",
"Error overlay for hydration errors in App router should show the highlighted bad nesting html snippet when bad nesting happened"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/invalid-imports.test.ts": {
"passed": [
"Error Overlay invalid imports should show error when external package imports client-only in server component",
"Error Overlay invalid imports should show error when external package imports server-only in client component",
"Error Overlay invalid imports should show error when require-ing client-only in server component",
"Error Overlay invalid imports should show error when using styled-jsx in server component"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/rsc-build-errors.test.ts": {
"passed": [
"Error overlay - RSC build errors importing 'next/cache' APIs in a client component cacheLife is not allowed",
"Error overlay - RSC build errors importing 'next/cache' APIs in a client component cacheTag is not allowed",
"Error overlay - RSC build errors importing 'next/cache' APIs in a client component revalidatePath is not allowed",
"Error overlay - RSC build errors importing 'next/cache' APIs in a client component revalidateTag is not allowed",
"Error overlay - RSC build errors importing 'next/cache' APIs in a client component unstable_cache is allowed",
"Error overlay - RSC build errors importing 'next/cache' APIs in a client component unstable_noStore is allowed",
"Error overlay - RSC build errors next/root-params importing 'next/root-params' in a client component",
"Error overlay - RSC build errors next/root-params importing 'next/root-params' in a client component in a way that bypasses import analysis",
"Error overlay - RSC build errors next/root-params importing 'next/root-params' when experimental.rootParams is not enabled",
"Error overlay - RSC build errors should allow to use and handle rsc poisoning client-only",
"Error overlay - RSC build errors should allow to use and handle rsc poisoning server-only",
"Error overlay - RSC build errors should error for invalid undefined module retuning from next dynamic",
"Error overlay - RSC build errors should error when Component from react is used in server component",
"Error overlay - RSC build errors should error when PureComponent from react is used in server component",
"Error overlay - RSC build errors should error when createContext from react is used in server component",
"Error overlay - RSC build errors should error when createFactory from react is used in server component",
"Error overlay - RSC build errors should error when flushSync from react-dom is used in server component",
"Error overlay - RSC build errors should error when unstable_batchedUpdates from react-dom is used in server component",
"Error overlay - RSC build errors should error when useActionState from react is used in server component",
"Error overlay - RSC build errors should error when useDeferredValue from react is used in server component",
"Error overlay - RSC build errors should error when useEffect from react is used in server component",
"Error overlay - RSC build errors should error when useEffectEvent from react is used in server component",
"Error overlay - RSC build errors should error when useFormState from react-dom is used in server component",
"Error overlay - RSC build errors should error when useFormStatus from react-dom is used in server component",
"Error overlay - RSC build errors should error when useImperativeHandle from react is used in server component",
"Error overlay - RSC build errors should error when useInsertionEffect from react is used in server component",
"Error overlay - RSC build errors should error when useLayoutEffect from react is used in server component",
"Error overlay - RSC build errors should error when useOptimistic from react is used in server component",
"Error overlay - RSC build errors should error when useReducer from react is used in server component",
"Error overlay - RSC build errors should error when useRef from react is used in server component",
"Error overlay - RSC build errors should error when useState from react is used in server component",
"Error overlay - RSC build errors should error when useSyncExternalStore from react is used in server component",
"Error overlay - RSC build errors should error when useTransition from react is used in server component",
"Error overlay - RSC build errors should freeze parent resolved metadata to avoid mutating in generateMetadata",
"Error overlay - RSC build errors should throw an error when \"Component\" is imported in server components",
"Error overlay - RSC build errors should throw an error when \"use client\" is on the top level but after other expressions",
"Error overlay - RSC build errors should throw an error when error file is a server component",
"Error overlay - RSC build errors should throw an error when error file is a server component with empty error file",
"Error overlay - RSC build errors should throw an error when getServerSideProps is used",
"Error overlay - RSC build errors should throw an error when metadata export is used in client components",
"Error overlay - RSC build errors should throw an error when metadata exports are used together in server components"
],
"failed": [],
"pending": [
"Error overlay - RSC build errors should throw an error when getStaticProps is used"
],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/rsc-runtime-errors.test.ts": {
"passed": [
"Error overlay - RSC runtime errors should show runtime errors if invalid client API from node_modules is executed",
"Error overlay - RSC runtime errors should show runtime errors if invalid server API from node_modules is executed",
"Error overlay - RSC runtime errors should show source code for jsx errors from server component"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/acceptance-app/server-components.test.ts": {
"passed": [
"Error Overlay for server components Class component used in Server Component should show error when Class Component is used",
"Error Overlay for server components Class component used in Server Component should show error when Component is rendered in external package",
"Error Overlay for server components Class component used in Server Component should show error when React.PureComponent is rendered in external package",
"Error Overlay for server components Next.js link client hooks called in Server Component should show error when useLinkStatus is called",
"Error Overlay for server components Next.js navigation client hooks called in Server Component should show error when useParams is called",
"Error Overlay for server components Next.js navigation client hooks called in Server Component should show error when usePathname is called",
"Error Overlay for server components Next.js navigation client hooks called in Server Component should show error when useRouter is called",
"Error Overlay for server components Next.js navigation client hooks called in Server Component should show error when useSearchParams is called",
"Error Overlay for server components Next.js navigation client hooks called in Server Component should show error when useSelectedLayoutSegment is called",
"Error Overlay for server components Next.js navigation client hooks called in Server Component should show error when useSelectedLayoutSegments is called",
"Error Overlay for server components React component hooks called in Server Component should show error when React client hook is called in external package",
"Error Overlay for server components React component hooks called in Server Component should show error when React.
while client routing should only execute async and defer scripts once", "updating
while client routing should update head during client routing", "updating
while client routing should update head when unmounting component", "updating
while client routing should update title during client routing", "updating
while client routing should warn when scripts are in head", "updating
while client routing should warn when stylesheets or scripts are in head" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, "test/development/pages-dir/client-navigation/index.test.ts": { "passed": [ "Client Navigation runtime errors should show redbox when a client side error is thrown inside a component", "Client Navigation runtime errors should show redbox when a client side error is thrown outside a component", "Client Navigation should emit routeChangeError on hash change cancel", "Client Navigation should handle boolean async prop in next/script client-side: false", "Client Navigation should handle boolean async prop in next/script client-side: true", "Client Navigation should handle undefined prop in head client-side", "Client Navigation should navigate to paths relative to the current page", "Client Navigation should not error on module.exports + polyfills", "Client Navigation should only execute async and defer scripts with next/script once", "Client Navigation should work on nested /index/index.js", "Client Navigation with URL objects should handle undefined in router.push", "Client Navigation with URL objects should work with \"Router.push\"", "Client Navigation with URL objects should work with ", "Client Navigation with URL objects should work with the \"replace\" prop", "Client Navigation with different types of urls should not work with /index page", "Client Navigation with different types of urls should work with / page", "Client Navigation with different types of urls should work with dir/ page", "Client Navigation with different types of urls should work with normal page", "Client Navigation with empty getInitialProps() should render a redbox", "Client Navigation with getInitialProp redirect should redirect the page via client side", "Client Navigation with getInitialProp redirect should redirect the page when loading", "Client Navigation with the HOC based router should navigate as expected", "Client Navigation with the current url should always replace the state", "Client Navigation with the current url should reload the page" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, "test/development/pages-dir/client-navigation/link.test.ts": { "passed": [ "Client Navigation with should call mouse handlers with an absolute url", "Client Navigation with should navigate an absolute local url", "Client Navigation with should navigate an absolute local url with as", "Client Navigation with should navigate an absolute url", "Client Navigation with should navigate back after reload", "Client Navigation with should navigate forwards after reload", "Client Navigation with should navigate the page", "Client Navigation with should navigate via the client side" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, "test/development/pages-dir/client-navigation/on-click.test.ts": { "passed": [ "Client navigation with onClick action should always replace the state and perform additional action", "Client navigation with onClick action should not reload if default was prevented", "Client navigation with onClick action should reload the page and perform additional action" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, "test/development/pages-dir/client-navigation/querystring.test.ts": { "passed": [ "Client navigation querystring with querystring relative urls router.replace with shallow=true shall not throw route cancelled errors", "Client navigation querystring with querystring relative urls should work with Link", "Client navigation querystring with querystring relative urls should work with router.push", "Client navigation querystring with querystring relative urls should work with router.replace", "Client navigation querystring with the same page but different querystring should navigate the page", "Client navigation querystring with the same page but different querystring should remove querystring" ], "failed": [], "pending": [], "flakey": [], "runtimeError": false }, "test/development/pages-dir/client-navigation/rendering-head.test.ts": { "passed": [ "Client Navigation rendering
custom meta properties are rendered only once", "Client Navigation rendering
header helper avoids dedupe of meta tags with the same name if they use unique keys", "Client Navigation rendering
header helper avoids dedupe of specific tags", "Client Navigation rendering
header helper dedupes tags", "Client Navigation rendering
header helper dedupes tags with the same key as the default", "Client Navigation rendering
header helper renders Fragment children", "Client Navigation rendering
header helper renders boolean attributes correctly children", "Client Navigation rendering
header helper renders header information", "Client Navigation rendering
header renders default charset", "Client Navigation rendering
header renders default viewport", "Client Navigation rendering
should handle undefined prop in head server-side", "Client Navigation rendering
should place charset element at the top of
"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/development/pages-dir/client-navigation/rendering.test.ts": {
"passed": [
"Client Navigation rendering Rendering via HTTP 404 should 404 on not existent page",
"Client Navigation rendering Rendering via HTTP 404 should 404 on wrong casing",
"Client Navigation rendering Rendering via HTTP 404 should not 404 for