-
Notifications
You must be signed in to change notification settings - Fork 63
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
log.message() doesn't work #66
Comments
Mhh, Could you give me some more information about your HTML & your test, as well as which browser you are using for your tests, your dalek, node & OS version? That would help me a lot debugging this issue. |
same for me: |
Hi @asciidisco, I have the same problem (log.message is simply ignored). I'll setup a testcase and check why it is not working as expected. OSX: 10.9.2 Best |
Hi @asciidisco, seems that outputLogUser in levelbase.js (console reporter) is empty, thus nothing is written to the stdout in the first 4 log levels (0 to 3). The method is overridden in log levels 4 + 5, thus the logging works fine there. Check this gist: https://gist.github.com/mdix/9666199 @asciidisco: If you can confirm that this is the root cause, I'll add a PQ that fixes the problem (I suppose just moving the method definition to loglevel 1 should be sufficient). Best Edit: nutting in level1 level4 |
@mdix I don't think there is an issue with outputLogUser as I believe that particular output is designed to only output at level 4 or higher (@asciidisco would be able to definitively confirm that). |
Fixed with mdix/dalek-reporter-console@2065c43 Will test & close if it works. |
Does this also mean, that the log messages will be forwarded to all reporter? |
You can build a reporter that receives the log messages & also outputs/saves them in any form. What you see in the console is also technically just a reporter. But as of now, the HTML reporter for example doesn't store the messages. |
(at least on Windows anyhow)
Whenever I try to use log.message(), in any form, the test either stalls when it reaches that instruction, or the test "ends" immediately displaying the current number of assertions, but without exiting the process (I need to Ctrl+Break to exit it), or it's simply skipped without outputting any messages at all.
I haven't been able to get any of the log features working at all (message() and dom()).
The text was updated successfully, but these errors were encountered: