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

Make WebGL jasmine tests run consistently across machines #241

Closed
etpinard opened this issue Feb 8, 2016 · 4 comments · Fixed by #1455
Closed

Make WebGL jasmine tests run consistently across machines #241

etpinard opened this issue Feb 8, 2016 · 4 comments · Fixed by #1455

Comments

@etpinard
Copy link
Contributor

etpinard commented Feb 8, 2016

More info in #240 and specifically in #240 (comment)

@etpinard etpinard added the feature something new label Feb 8, 2016
etpinard added a commit that referenced this issue Feb 16, 2016
 - these will only run locally at the moment as
   and until #241
   is resolved.
@etpinard etpinard added type: maintenance and removed feature something new labels Apr 14, 2016
@etpinard
Copy link
Contributor Author

Making our gl jasmine test work on CircleCI is getting more and more critical.

I'll give it a shot this at some point this week. I'm hoping that using xvfb in a similar way to this project will get us close.

@etpinard
Copy link
Contributor Author

etpinard commented Sep 30, 2016

might be of interest.

So maybe using Chromium + karma on CircleCI with a few extra flags would work.

@etpinard
Copy link
Contributor Author

etpinard commented Mar 7, 2017

As per issues

a karma-based solution should be made possible in the not-so-far future.

@etpinard
Copy link
Contributor Author

etpinard commented Mar 7, 2017

I think I'm on to something here

https://gist.github.com/etpinard/f328c38536360ff37c0de62172c01617

This thing

https://github.com/CodeYellowBV/run-headless-chromium

might be exactly what we need.


WebGL jasmine tests on CI by week's end? Maybe ... see the run-headless-chromium branch.

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

Successfully merging a pull request may close this issue.

1 participant