-
Notifications
You must be signed in to change notification settings - Fork 8
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
Run tests on ci.testling.com #27
Comments
I would love to get a pull request 😄 |
Then I have to touch your weird test framework that you havn't touched in 18 months and it has weird exports things and it doesnt output tap! Port your tests to use substack/tape and i'll get it working on ci.testling :D |
I don't mind pull request that rewrites test to tape too :D |
What your running shit in phantomify? That's MADNESS |
I'm going to see whether your tests run in testem at some point. although I may do that with reflex instead |
No it's great for testing node code on headless webkit without any code changes that also works on travis.ci |
oh lol. duplicate. |
Integrating testling-ci integration tests. #27
Ok I have being trying to setup testling.ci but for unknown reasons test won't even run |
@Gozala bitch at @substack about them using an old version of browserify |
I think it may be related to the fact that timers module was not found for testling.ci trying to workaround this now. |
ok finally tests are running but still something strange is going on. It also looks like only subset of tests run ... |
I have manually compiled test file with browserify and run test on FF, Chrome, Safari and Opera. All tests seem to pass fine not sure what's wrong with ci.testling |
I'm not sure :(. I asked in #browserling |
@substack It seems to me that tests still don't run as expected, chrome stops running at random points and other the IE tests not even run in other browsers. Is it some other issue now or the fix did not quite fixed it ? |
http://ci.testling.com/
I want to see the browser support matrix for reducers.
The text was updated successfully, but these errors were encountered: