Example using Jest and Cypress with TypeScript in a single repo
If you are using Jest and Cypress types in the same project, they might conflict because both test runners use globals like expect. This project shows how to isolate Cypress TypeScript definitions from Jest TS definitions in the same project.
See the root level tsconfig.json and jest.config.js. The Cypress types are isolated from the root in the file cypress/tsconfig.json. The root tsconfig explicitly only includes libs with Jest globals (without Cypress)
While writing the production code, we want to limit ourselves to the src TS files without including the spec files. While linting, we want to lint all files. Thus we create a separate tsconfig.lint.json file that includes all src files, but sets noEmit: true compiler option. The command npm run lint thus lints src folder, without Cypress files.
To lint Cypress specs, we have a separate lint command that points at cypress/tsconfig.json file.
{
"scripts": {
"build": "tsc",
"lint": "tsc --project tsconfig.lint.json",
"lint:cypress": "tsc --project cypress/tsconfig.json"
}
}See the excellent advice on setting TypeScript for Jest and Cypress in TypeScript Deep Dive e-book by Basarat Syed
- Using Jest with TypeScript
- Cypress E2E with TypeScript
- Cypress TypeScript transpilation is using built-in TS support
If you hit a problem using Jest and Cypress in the same project, please open an issue in this repository. Include a fork of this repository that shows the problem.
This project is licensed under the terms of the MIT license.