Automated testing #3
Description
From @mstade on September 16, 2015 14:53
Rhumb needs to work in some set of browsers, but testing these can be a pain. To make sure things are working correctly, we need to set up automated testing across whatever set of browsers are relevant. (That's a different discussion, which doesn't much affect the core of this issue.) At minimum, this set up must work with whatever CI we set up; but ideally we'd also have the same (or at least similar) capabilities in local development.
BrowserStack and SauceLabs are popular alternatives for hosted browser testing, and both provide free plans for OSS projects. Additionally, there are plenty of tools available to make use of either of these services. @pemrouz has developed Popper, which looks mighty interesting for realtime browser testing, definitely worth looking into.
Additionally, rhumb should work in a non-browser setting, with the minimum support level being Node and should it run in things like Nashorn that's just a bonus. Thus, any tests run in a browser should work outside of a browser as well.
Copied from original issue: sammyt/rhumb#8