71c21dfc9a
This allows us to set breakpoints and debug e2e tests without encountering a timeout after 60 seconds. For example, using: ``` NEXT_E2E_TEST_TIMEOUT=1000000 NODE_OPTIONS=--inspect-brk pnpm test-dev test/e2e/app-dir/metadata/metadata.test.ts ``` Notably, this change also affects the turbopack dev tests in the CI, where `NEXT_E2E_TEST_TIMEOUT` is currently set to 240 seconds. Since the same env variable is also used for `jest.setTimeout()`, a test timeout will now most likely occur due to jest timing out, and not a specific playwright check (i.e. `waitForElementByCss` or `waitForCondition`) timing out. This sounds acceptable to me. Co-authored-by: JJ Kasper <jj@jjsweb.site> |
||
---|---|---|
.. | ||
browsers | ||
next-modes | ||
test-data-service | ||
amp-readme.md | ||
amp-test-utils.js | ||
amp-validator-wasm.js | ||
create-next-install.js | ||
development-sandbox.ts | ||
e2e-utils.ts | ||
next-test-utils.ts | ||
next-webdriver.ts | ||
react-channel-require-hook.js | ||
test-log.ts | ||
turbo.ts | ||
use-temp-dir.ts |