-
Notifications
You must be signed in to change notification settings - Fork 142
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
Mocha Spec Reporter #234
Comments
I suspect mocking console.log is not going to end well for you, since lots of other libraries (including Mocha) will call I recommend wrapping console.log to your own logger and mocking that. See this article. That's what we do in this lib here |
I am totally with you and I just want to point out that I took a photo of that failed test to prove I can make the test fail. In the first photo the tests are 'passing' but no check marks are showing up in the reporter. |
I'm sorry, I do not understand what your issue is. I don't know what the checkmarks you're looking for are. |
To my earlier comment I will mock something other than console.log and see if I can get the same behavior. In the explain test suite I have 3 tests that use testdouble. They are all passing but not showing up in the reporter. |
Could you please provide a minimal example project repo |
Yeah I will make one and follow up if needed. Thanks for your time! |
I feel like this might be a little OCD but I have noticed something weird when using testdouble and mocha. I am going to put an excerpt of one of my tests.
The test passes but the spec reporter doesn't show one of the check marks
I know things are technically working because if I change something in the test to make it break it does cause Mocha to fail.
PS. For what it is worth I love your explain functionality of testdouble and I have a feature in the library I am creating that shows off the influence. 😄
The text was updated successfully, but these errors were encountered: