Skip to content
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

Open
soonick opened this issue Jul 14, 2013 · 8 comments
Open

Test results not printing properly #250

soonick opened this issue Jul 14, 2013 · 8 comments

Comments

@soonick
Copy link
Contributor

soonick commented Jul 14, 2013

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:

socket.on('results', _.bind(self.onResults, self));

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

@sethmcl
Copy link
Contributor

sethmcl commented Jul 15, 2013

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:

venus run -t examples/ -n

Output seems to be as expected.

Thanks!
Seth

@soonick
Copy link
Contributor Author

soonick commented Jul 15, 2013

Hey Seth,

I just pulled the latest again and tried running the examples:

venus_examples

As you can see it says 0 tests executed, 0 passed and 0 failed.

@sethmcl
Copy link
Contributor

sethmcl commented Jul 15, 2013

Can you try running: venus run -t examples/ -n --hostname localhost to
see if that fixes it?

On Sun, Jul 14, 2013 at 6:14 PM, Adrian Ancona Novelo <
notifications@github.com> wrote:

Hey Seth,

I just pulled the latest again and tried running the examples:

[image: venus_examples]https://f.cloud.github.com/assets/281836/795246/b41fe7a0-eceb-11e2-8dfa-726c369a170a.png

As you can see it says 0 tests executed, 0 passed and 0 failed.


Reply to this email directly or view it on GitHubhttps://github.com//issues/250#issuecomment-20948155
.

@soonick
Copy link
Contributor Author

soonick commented Jul 16, 2013

Hey Seth,

I tried your suggestion but I get the same output.

Regards,
Adrian

@sethmcl
Copy link
Contributor

sethmcl commented Jul 16, 2013

Is this on a Mac? Can you try rerunning npm install?

On Monday, July 15, 2013, Adrian Ancona Novelo wrote:

Hey Seth,

I tried your suggestion but I get the same output.

Regards,
Adrian


Reply to this email directly or view it on GitHubhttps://github.com//issues/250#issuecomment-21019941
.

@soonick
Copy link
Contributor Author

soonick commented Jul 16, 2013

Hey Seth,

I deleted the node_modules folder and ran npm install again but the problem persists. This is my personal Linux computer.

Regards,
Adrian

@sethmcl
Copy link
Contributor

sethmcl commented Jul 16, 2013

Is this only with phantom? Do tests run in the browser?

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,
Adrian


Reply to this email directly or view it on GitHubhttps://github.com//issues/250#issuecomment-21022744
.

@soonick
Copy link
Contributor Author

soonick commented Jul 16, 2013

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants