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

Using --forceExit and --coverage exits before coverage is reported Jest@20 #3555

Closed
tolu opened this issue May 11, 2017 · 3 comments
Closed

Comments

@tolu
Copy link

tolu commented May 11, 2017

Do you want to request a feature or report a bug?

bug

What is the current behavior?

When executing tests with --coverage and --forceExit flags, the process exits before coverage is reported. Dropping --forceExit reports coverage but the process never exits (at least on windows in one of my projects, but I haven't gotten to the bottom of that yet).
This worked as expected in 19.0.2, but fails in 20.0.1.

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.

What is the expected behavior?

Using --forceExit with --coverage should report coverage before exiting (or at least offer a warning).

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

Node 7.10.0
Yarn 0.23.4
Npm 4.2.0

Minimal repo for reproducing the behaviour (on both win and mac)
https://github.com/tolu/jest-coverage-bug
Just yarn && yarn test and see that no coverage is reported

@thymikee
Copy link
Collaborator

Not super sure, but this might get fixed with #3554

@tolu
Copy link
Author

tolu commented May 11, 2017

Just tested with my case by manipulating local jest with changes from #3554 and it seems to work perfectly!

Thanks!

@tolu tolu closed this as completed May 11, 2017
@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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants