Popper!

[pemrouz]

Just run popper (or popper -b, where -b means an empty list of browsers, which overrides the list of browsers in the .popper.yml, which basically means, don't spawn any browsers in BrowserStack for this run, which is useful if you are just running locally).

This is what :1945/dashboard looks like (note: kept dashboard UI simple, so it just categorises by top-level describes - I prefer having a flatter list so I can see more rows):

This is what the test agents on :1945 look like:

This is what npm test looks like (i.e. results from Travis):

This is what running the same tests on node via npm test-node (i.e. mocha) looks like (it;s on the roadmap to have popper pull these results into the same dashboard):

[pemrouz]

For some reason, your mkdir -p lib was creating a -p and lib folder for me. Probably because Windows..

[mstade]

Yeah most def because windows. :o)

[mstade]

This is very cool – thanks buddy! However, I'm right in the process of moving to tape instead of mocha. There are various reasons for this, but composability is a major one. I opened up pemrouz/popper#6 because of that. Currently looking to see if there's anything I can do to help, it's a very nifty tool you've written.

[pemrouz]

Awesome, well this was super simple to do. Just had to point popper to your test.rhumb.js. Let's take another look once you've checked in the new tape tests.

[mstade]

I can do that right now, gimme a sec!

[mstade]

Alright, pushed the new tests (see #11.)

[mstade]

This issue was moved to websdk/rhumb#8