Skip to content
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

Don't run globalSetup if no test suites need to be run #5315

Closed
mxstbr opened this issue Jan 15, 2018 · 2 comments · Fixed by #5323
Closed

Don't run globalSetup if no test suites need to be run #5315

mxstbr opened this issue Jan 15, 2018 · 2 comments · Fixed by #5323

Comments

@mxstbr
Copy link
Contributor

mxstbr commented Jan 15, 2018

Feature request

What is the current behavior?

I start my tests with no changes to the codebase, Jest says "determining test suites to run" and then "No tests found related to files changed since last commit". While it's determining the test suites to run the globalSetup module is executed.

What is the expected behavior?

The globalSetup module is only executed if tests will be run.

Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.

MacOS High Sierra and

$ cat node_modules/jest/package.json | grep version
"version": "22.1.0"
$ yarn -v
1.3.2
$ npm -v
5.5.0
@SimenB
Copy link
Member

SimenB commented Jan 15, 2018

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants