This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 213
neutrino test always exits with 0 #632
Labels
Comments
Also the coverage report is gone between v6 and v7 |
Looks like 3d7ea84 broke it since Jest |
Trying to dig into the Jest changelog, but nowhere did it mention this breaking change. I found the part of the commit that broke this: Unfortunately the commit message is only "Refactor CLI", and didn't mention at all how the API had changed here, so this was missed. Apologies. |
Oh wow! Nothing to apologize. Let's try to cover this with tests to prevent in the future |
Just to address the issue title: the |
eliperelman
pushed a commit
that referenced
this issue
Dec 21, 2017
timkelty
pushed a commit
to timkelty/neutrino
that referenced
this issue
Jan 17, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using Jest preset, even if my test suit fails the exit code is always 0 which causes CI to always pass.
neutrino version 7.2.1+ (also tested on 7.4.0)
It works as expected on v6.2.0
The text was updated successfully, but these errors were encountered: