Browser CI Setup

[megawac]

This sets up browser continuous integration and fixes #923.

Some issues I've encountered in this configuration:

• parallel tests will sometimes fail without karma/mocha catching it properly, causing tests to stall

• Queue pause tests often error.

@aearly email me/ping me on gitter if you want testingbot keys to run tests locally

[testingbot]

Should be public: true

[aearly]

Why don't we test Firefox/Safari/IE instead of Chrome for now. I've messed around with CI systems in the past, and have noticed that Chrome will randomly hang in a containerized environment occasionally. We get pretty good V8 coverage through node.

[megawac]

@aearly having similar issues with the queue tests in Firefox and Safari. I notice these tests are using a bunch of setTimeouts. Could the issue be that the vm is slower than expected?

[aearly]

Bah, debugging tests that only fail in a CI browser environment is one of my personal visions of hell.

Yes, it's very possible that the setTimeouts are much slower than anticipated. I would love to figure out a way to test that didn't rely on timings at all. One long GC pause, or any other CPU hang, and everything goes out the window.

[jdalton]

^ Duplicate Edge entry.

[aearly]

Shall I close this? Seems really out of date.

[megawac]

Em... I still want to get this in. It just sort of needs #1322 to be resolved. Guess its probably fine to close for now and work on later.

[megawac]

I'm going to leave the branch hanging around though.

[ferdian26]

Check