Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

CI mode hangs if no test results reported #140

Closed
Raynos opened this Issue · 4 comments

2 participants

@Raynos

https://gist.github.com/4350158

The phantomjs tests outputs TAP to console.log (stdout) but doesn't communicate with the testem server.

The ci command just hangs and doesn't do anything.

A useful default would be for it to just print the stdout TAP info.

@airportyh
Owner

Yup. Bug.

@airportyh
Owner

Take that back, not necessarily a bug. In this case since it's browser tests, the test runner is waiting for the socket.io events to come, which never will. For your case, you just need to get a tap-writing test runner working, let's work on that and this will naturally sort itself out.

@airportyh
Owner

Although this begs the question of: if you just want to use testem to run a script which does not report any test results at all (you just want to see its output to stdout or console.log), what should it do in ci mode? Thoughts?

@airportyh airportyh closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.