Skip to content

Add tip on cypress.config.ts to testing-and-auditing documentation #17561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

joshbuker
Copy link
Contributor

If you use both Cypress and another testing framework that implements expect and other common keywords, you may need to exclude cypress.config.ts from your tsconfig.json to prevent ESLint from getting confused.

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Documentation
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

The PR fulfills these requirements:

  • It's submitted to the dev branch (or v[X] branch)
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • It's been tested on a Cordova (iOS, Android) app
  • It's been tested on an Electron app
  • Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

If you use both Cypress and another testing framework that implements `expect` and other common keywords, you may need to exclude `cypress.config.ts` from your `tsconfig.json` to prevent ESLint from getting confused.
@joshbuker
Copy link
Contributor Author

Copy link

@arnonrdp arnonrdp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this.

@yusufkandemir
Copy link
Member

Hi, thanks for contributing 👏 If this problem and solution still exist, the snippet needs to be updated to utilize quasar.config.ts > build > extendTsConfig instead.

But, I believe it would be better to mention or even automatically handle this in https://github.com/quasarframework/quasar-testing

/cc @IlCallo

@IlCallo
Copy link
Member

IlCallo commented May 26, 2025

This happens when using two frameworks which leverage global types functions with the same name, it's a know issue

While Cypress doesn't really allow to avoid this AFAIK, Jest and Vitest do provide helpers to explicitly import those functions

We scaffold Jest and Vitest AE files to avoid using global types, and you should too: https://github.com/quasarframework/quasar-testing/tree/dev/packages/unit-jest#import-jest-helpers-from-jestglobals-optional-but-strongly-recommended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants