-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
request/question: How to access debug log stream #716
Comments
Definitely ephemeral, but you can override the Check out #556 which would solve a lot of the testing needs, too. Not sure when it will be implemented. Does that help? |
Thank you for the quick response. Yes, your insight is extremely helpful. I'll explore further. Else I'll implement some version of #192 . |
Right now the ugly hack for Node would be to pass all of those strings to |
Sounds fun. I'll get my hands dirty. Also, it just occured to me that it may prove effective to wrap a sinon spy around the debug function, then do a getCalls().args on it. I'll let you know how that pans out for the benefit of others. But otherwise you may close the issue. |
You can definitely do that. Keep in mind, however, that depending on how you're using |
Thank you. I willl :) |
Greetings. Thank you for the amazing library. I'm curious as to how to access this libraries standard output and error stream. Is it printed and ephemeral or is it written to a file. My intention is to assert in my tests whether something was logged. Any insight would be much appreciated.
The text was updated successfully, but these errors were encountered: