65369991d8
So there are some toBe property's with React-testing-library that when written shows this error for example: Property 'toBeInTheDocument' does not exist on type 'JestMatchers<HTMLElement>'. the commit fixes it✅ <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Co-authored-by: Sam Ko <sam@vercel.com> |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| app | ||
| pages | ||
| public | ||
| styles | ||
| .gitignore | ||
| jest.config.js | ||
| jest.setup.js | ||
| next-env.d.ts | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| types.d.ts | ||
Next.js + Jest
This example shows how to configure Jest to work with Next.js.
This includes Next.js' built-in support for Global CSS, CSS Modules and TypeScript. This example also shows how to use Jest with the App Router and React Server Components.
Note: Since tests can be co-located alongside other files inside the App Router, we have placed those tests in
app/to demonstrate this behavior (which is different thanpages/). You can still place all tests in__tests__if you prefer.
Deploy your own
How to Use
Quickly get started using Create Next App!
In your terminal, run the following command:
npx create-next-app --example with-jest with-jest-app
yarn create next-app --example with-jest with-jest-app
pnpm create next-app --example with-jest with-jest-app
Running Tests
npm test