Pedram Emrouznejad
Pedram Emrouznejad
This actually deletes the code that attempts to parse functions in favour of a simpler technique (originally used in [utilise/fn](https://github.com/utilise/fn/blob/master/index.js)) which means all the newer features like classes and arrow...
I was just wondering if anyone has looked into adding this before and not done it for any reason, and if not, @hunterloftis would you accept a PR to add...
Add support for detecting a `.popperrc` to set global defaults. These should still be overriden by per-project YAML files (.popper.yml) and also CLI flags.
The logs page streams in the results from test agents. We could also allow the user to execute commands on the test agent from here.
Add a link to jump into interactive session on BrowserStack/Sauce if still running
Aggregate over multiple trials to address known variance issues in client-side testing
Add an option to allow running the test file in Node and aggregate the results in the dashboard
In true Kappa style, it would be nice to create a module (and host it somewhere) that takes some [travis](https://travis-ci.org/rijs/precss#L1368) [results](https://travis-ci.org/vanillacomponents/ux-button/builds/107574892#L1353) and from the `browser passed/failed` lines generates an image...
Add simple duration stats for each test using [perf](https://github.com/utilise/utilise#--perf)