-
Notifications
You must be signed in to change notification settings - Fork 44
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
Test results not printing properly #250
Comments
Hi Adrian, Could you provide some more details on the output you are seeing? It seems to be working fine for me. I just pulled master and ran this command to test:
Output seems to be as expected. Thanks! |
Can you try running: On Sun, Jul 14, 2013 at 6:14 PM, Adrian Ancona Novelo <
|
Hey Seth, I tried your suggestion but I get the same output. Regards, |
Is this on a Mac? Can you try rerunning npm install? On Monday, July 15, 2013, Adrian Ancona Novelo wrote:
|
Hey Seth, I deleted the node_modules folder and ran npm install again but the problem persists. This is my personal Linux computer. Regards, |
Is this only with phantom? Do tests run in the browser? On Monday, July 15, 2013, Adrian Ancona Novelo wrote:
|
Tests run correctly in the browser. It also seems like the tests run correctly in phantom but since onResults is never executed the output is incorrect. |
Hey Seth,
I got the latest from master today and I noticed that the reporter was not giving me correct information. I looked a little into the code and it seems like onResults is never being called on executor.js.
It seems like it should be called when the results event is emitted in the socket:
But I couldn't find where that event was supposed to be emitted. Can you please look into this when you have some time?
Thanks,
Adrian
The text was updated successfully, but these errors were encountered: