eb0bd63af4
This fixes our `basePath` detection/replacing server-side as we were incorrectly considering `/docss` a match for a `basePath` of `/docs` which caused us to have an unexpected value in the `normalizeLocalePath` function. - Fixes #22429 - Regression introduced in #17757 - Fixes: https://github.com/vercel/next.js/issues/31423 Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .stats-app | ||
| development | ||
| e2e | ||
| integration | ||
| lib | ||
| production | ||
| unit | ||
| .eslintrc.json | ||
| .gitignore | ||
| jest-setup-after-env.ts | ||
| readme.md | ||
| test-file.txt | ||
Writing tests for Next.js
Test types in Next.js
- e2e: These tests will run against
next devandnext 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
waitForElementor using thecheckutil innext-test-utils. - When applying a fix, ensure the test fails without the fix. This makes sure the test will properly catch regressions.