Mike Johnson
Mike Johnson
It would be nice if this could get merged already. It fixes a lot of things.
I'm planning to try to implement this. I don't have UI/UX design ideas of my own that I'm sold on, though. If anyone has ideas for a design, please tell...
I'm not sure. The current test uses QUnit, and I have no experience with QUnit and Travis-CI.
Of course! - In the `test` directory, use Go to build `server.go` and run it. - In the `test/test` directory, use GopherJS to build `index.go` -> `index.js` - In a...
I concur. But, don't we need a browser in order to test this? I don't believe Node has a standards compliant WebSocket implementation built-in. Perhaps PhantomJS?
Came across this while browsing around for another project: http://swizec.com/blog/how-to-run-javascript-tests-in-chrome-on-travis/swizec/6647
I had thought about this the other day and came across Selenium. Travis CI has a guide to using Sauce Labs for Selenium testing. Sauce Labs provides free services for...
> For code quality checking, do you mean running `gofmt -d -s` and `go tool vet .` (like I [normally do](https://github.com/shurcooL/gostatus/blob/97e8adbc5da9bb3524e66e04d43deb84a42b35a1/.travis.yml#L14-L15) in all my Go repositories) to make sure they...
Should we have one Sauce Labs team for all of the GopherJS projects that need browser tests? Should we write a more idiomatic library for running GopherJS tests on Sauce...
> Should we write a more idiomatic library for running GopherJS tests on Sauce Labs? I just found `gopherjs test -c`, so all we'd need is a little bit of...