The extracted test started timing out in https://github.com/vercel/next.js/pull/65058. When it does, it leaves the whole test suite in a corrupted state and fails all subsequent tests.
The slow part was just immediately stopping. It also wasn't robust against test failures since the cleanup logic was in the test itself not beforeEach or afterEach.
I moved the test to a separate describe block where tests don't start with a started Next.js server. This saves time and isolates failing tests.
The extracted test started timing out in https://github.com/vercel/next.js/pull/65058. When it does, it leaves the whole test suite in a corrupted state and fails all subsequent tests.
The slow part was just immediately stopping. It also wasn't robust against test failures since the cleanup logic was in the test itself not
beforeEach
orafterEach
.I moved the test to a separate describe block where tests don't start with a started Next.js server. This saves time and isolates failing tests.
Closes NEXT-3280