Unverified Commit 331a4692 authored by Jamiboy Mohammad's avatar Jamiboy Mohammad Committed by GitHub

test: enable log-file and worker-react-refresh in deploy mode (#100480)

## Summary

Removes the `TODO(deploy-test-completion)` exclusion from two suites
that already pass against a Vercel deployment:

- `test/e2e/app-dir/log-file/log-file.test.ts` — passed in 6 deploy jobs
(normal and Cache Components, 55–75s each) when its gate was removed in
the Sept 9 retry runs, e.g. [run
34404668278](https://github.com/vercel/next.js/actions/runs/34404668278)
and [run
34404667354](https://github.com/vercel/next.js/actions/runs/34404667354).
The browser-log assertions run for real; the `next-development.log`
check in the non-dev branch only asserts the log file is absent, which
also holds for a deployment.
- `test/e2e/worker-react-refresh/worker-react-refresh.test.tsx` — passed
in both deploy variants (~60s each) of [run
36052929022](https://github.com/vercel/next.js/actions/runs/36052929022)
from #99187.

Both files are unchanged since those runs apart from the gate itself and
a dev-only snapshot line.

Three other suites that looked green in the same runs are not included:
`404-page-router`, `draft-mode`, and `app-dir/actions/app-action-export`
each had an in-file `isNextDeploy`/`!isNextStart` early return at the
time, so the deploy job only ran a placeholder test.

## Verification

- Checked neither suite is listed in `test/deploy-tests-manifest.json`.
- Not run locally in deploy mode (no `VERCEL_TEST_TOKEN` locally); this
PR's deploy job covers it.

<!-- NEXT_JS_LLM -->
parent e56e53c9
......@@ -3,9 +3,6 @@ import path from 'path'
import { nextTestSetup } from 'e2e-utils'
import { retry } from 'next-test-utils'
// TODO(deploy-test-completion): Re-enable this suite in deploy mode.
// It likely reads files from the isolated local fixture.
// @force-gate !deploy
describe('log-file', () => {
const { next, isNextDev } = nextTestSetup({
files: __dirname,
......
import { nextTestSetup } from 'e2e-utils'
// TODO(deploy-test-completion): Re-enable this suite in deploy mode.
// No deploy-specific incompatibility is documented.
// @force-gate !deploy
describe('worker-react-refresh', () => {
const { next } = nextTestSetup({
files: __dirname,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment