Ben Loveridge
Ben Loveridge
I encountered this issue as well using jasmine via grunt-jasmine-nodejs. The above workaround seems to be working great for now, inside a helper file loaded before the specs.
It’s not intentional. I’d need to go re read the spec again, but I suspect failures is supposed to represent the number of specs (it) that failed, not the number...
Were you ever able to find a solution to this issue?
Each of the current reporters were created to fill a specific need or workflow, and were mostly contributed by community members who had the need and wanted to share the...
I'm sorry you have experienced problems. Please consider creating a pull request with appropriate improvements and I'd be happy to include those and produce a new build.
Did you review and consider my comments from a few months back? I’m hesitant to add another way of modifying something that’s already exposed for user control. Am I missing...
I tried to use the GitHub pull request review feature, which maybe I didn't utilize correctly... it looks like it might have just posted the comments now, because I never...
I've never used jest, so I'm not sure if there's something environmental going on there—I may take a stab at setting it up just to try. To see if there...
Can you confirm the behavior still exists for you with v2.2.0 of jasmine-reporters?
From the Jest troubleshooting guide: > Note: the --runInBand cli option makes sure Jest runs test in the same process rather than spawning processes for individual tests. Normally Jest parallelizes...