archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/test
History
JJ Kasper 55d8a14e8a
Fix flakey next/link react streaming test (#32351) 
x-ref: https://github.com/vercel/next.js/runs/4477101349?check_suite_focus=true
x-ref: https://github.com/vercel/next.js/runs/4475354509?check_suite_focus=true
x-ref: https://github.com/vercel/next.js/runs/4474805941?check_suite_focus=true
2021-12-10 07:43:55 +00:00
..
.stats-app Remove extra config for PR stats (#30478) 2021-10-27 14:30:39 -05:00
development Add test for TailwindCSS JIT mode reloading (#32130) 2021-12-04 21:59:32 +00:00
e2e Fix non-concurrent function _document (#31628) 2021-11-19 19:41:19 +00:00
integration Fix flakey next/link react streaming test (#32351) 2021-12-10 07:43:55 +00:00
lib Fix copying swc binary for isolated tests locally (#32026) 2021-12-02 13:40:38 +01:00
production Ensure conf type for createServer is not changed (#32134) 2021-12-04 22:57:54 +00:00
unit Fix crash in no-page-custom-font eslint rule when default export is unnamed. (#32251) 2021-12-07 19:04:24 +00:00
.gitignore Universal Webpack (#3578) 2018-01-30 16:44:44 +01:00
jest-setup-after-env.ts Update test set-up to leverage playwright when able to (#28634) 2021-09-13 14:36:25 +02:00
readme.md Update test set-up to leverage playwright when able to (#28634) 2021-09-13 14:36:25 +02:00
test-file.txt Add additional file serving tests (#12479) 2020-05-04 11:58:19 -05:00

readme.md

Writing tests for Next.js

Test types in Next.js

  • e2e: These tests will run against next dev and next start
  • development: These tests only run against next dev
  • production: These tests will run against next start.
  • integration: These tests run misc checks and modes and is where tests used to be added before we added more specific folders. We should not add any more tests here.
  • unit: These are very fast tests that should run without a browser or running next and should be testing a specific utility.

For the e2e, production, and development tests the createNext utility should be used and an example is available here. This creates an isolated Next.js install to ensure nothing in the monorepo is relied on accidentally causing incorrect tests.

All new tests should be written in TypeScript either .ts (or .tsx for unit tests). This will help ensure we catch smaller issues in tests that could cause flakey or incorrect tests.

Best practices

  • When checking for a condition that might take time, ensure it is waited for either using the browser waitForElement or using the check util in next-test-utils.
  • When applying a fix, ensure the test fails without the fix. This makes sure the test will properly catch regressions.