rsnext/test/jest-setup-after-env.ts

// @ts-ignore
import * as matchers from 'jest-extended'
expect.extend(matchers)

// A default max-timeout of 90 seconds is allowed
// per test we should aim to bring this down though
jest.setTimeout((process.platform === 'win32' ? 180 : 120) * 1000)
type check tests (and convert next-test-utils.js to ts) (#51071) Enables type checking for tests in CI and fixes a bunch of things related to that 2023-06-23 19:42:50 +02:00			`// @ts-ignore`
Adds tests to ensure `eslint-plugin-next`'s available rules are properly exported and recommended rules are correctly defined. (#38183) * Adds tests to ensure `eslint-plugin-next`'s available rules are properly exported and recommended rules are defined correctly. * Condenses imports. * Sets default recommended value. * replace Object.hasOwn for node 14 Co-authored-by: JJ Kasper <jj@jjsweb.site> 2022-06-30 18:31:33 +02:00			`import * as matchers from 'jest-extended'`
			`expect.extend(matchers)`

Update test set-up to leverage playwright when able to (#28634) Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> 2021-09-13 14:36:25 +02:00			`// A default max-timeout of 90 seconds is allowed`
			`// per test we should aim to bring this down though`
Increase CI test timeout (#47973) Seems builds in CI have been timing out with the 90s limit and with the shared concurrency of the limited CPUs additional time may be needed to avoid retrying un-necessarily. x-ref: https://github.com/vercel/next.js/actions/runs/4620023451/jobs/8170530943 x-ref: https://github.com/vercel/next.js/actions/runs/4619675493/jobs/8168849370 2023-04-05 19:16:48 +02:00			`jest.setTimeout((process.platform === 'win32' ? 180 : 120) * 1000)`