Enable deploy tests for reusable fixture variants (#99404)
## Summary Enable deploy tests for the six remaining fixture-reuse files: the conflict/group not-found routes, missing-Suspense and browser-bailout variants, dynamic optional routing, and both middleware source-location suites. Prepare each production variant before startup instead of patching, renaming, cleaning, or rebuilding the same fixture. Remove the file-level deployment skips while preserving every production assertion and the existing dev file-mutation checks. Failed builds use rejected startup with the same diagnostics; static-export tests check the same warning after a local build or deployment. Forward the browser-bailout flag explicitly to remote builds. The middleware static-export fixtures explicitly disable Cache Components and its dependent cached navigations flag, since static export does not support PPR; both suites still execute their full build and warning assertions in the Cache Components CI jobs. ## Verification - Turbopack and Webpack production runs: 7 test entry points and 45 tests passed in each, including the browser-bailout wrapper. - Turbopack and Webpack dev runs: 5 applicable entry points and 43 tests passed in each; the two existing production-only skips are unchanged. - TypeScript, ESLint, and Prettier passed. - Additional Cache Components runs: both Suspense variants passed with both bundlers. The two not-found files reproduce their existing incompatibilities (Edge runtime; the conflict fixture also uses an unguarded timestamp) and retain their existing Cache Components manifest exclusions. No new skips are added. - Reproduced all four middleware static-export failures with the Cache Components CI feature flags. After the fixture fix, both suites pass all four cases with Turbopack and Webpack under those flags. - Standard deploy CI passed. Local deploy verification is blocked by the Vercel project permissions; the corrected Cache Components deploy cases await the new CI run. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment