-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Move test summary to after coverage report #4104
Labels
Comments
hramezani
added a commit
to hramezani/jest
that referenced
this issue
Sep 19, 2017
hramezani
added a commit
to hramezani/jest
that referenced
this issue
Oct 7, 2017
cpojer
pushed a commit
that referenced
this issue
Feb 7, 2018
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Do you want to request a feature or report a bug? Feature/enhancement
What is the current behavior? Currently when you run jest with
--coverage
the output looks something like this.What is the expected behavior? I think it'd be nicer as a user if the results summary was always the bottom of the output, I always want to be able to know the general outcome of my test run regardless of whether the coverage report was made or not.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
The text was updated successfully, but these errors were encountered: