Commit graph

408 commits

Author SHA1 Message Date
greenkeeperio-bot
827e37f3d4 chore(package): update lockfile
https://npm.im/greenkeeper-lockfile
2018-02-23 19:45:24 +00:00
greenkeeperio-bot
f78333a544 chore(package): update lockfile
https://npm.im/greenkeeper-lockfile
2018-02-23 14:52:01 +00:00
greenkeeperio-bot
b91248719a chore(package): update lockfile
https://npm.im/greenkeeper-lockfile
2018-02-22 14:43:12 +00:00
greenkeeperio-bot
a3a5ce9aa4 chore(package): update lockfile
https://npm.im/greenkeeper-lockfile
2018-02-21 22:49:21 +00:00
greenkeeperio-bot
b9df9d6981 chore(package): update lockfile
https://npm.im/greenkeeper-lockfile
2018-02-21 11:29:40 +00:00
greenkeeperio-bot
70a5fb99d4 chore(package): update lockfile
https://npm.im/greenkeeper-lockfile
2018-02-20 23:26:23 +00:00
Jérémie Astori
9c4ea85041 Instrument client code before running tests
Despite being a bit gross to look at, this brings a few advantages:

- Tests are now closer to what actually runs, so more likely to find broken stuff.
- We can start using things that were so far Webpack-only or browser-only, like ES6 imports, loading Handlebars templates, etc.
- We open ourselves to browser testing (there is some work to do, but that would be a necessary step).
- We improve the client/server separation, by making it possible to run them independently

I do some extra steps around coverage: now we have 2 reports (client + server), so I have an extra step to combine them (the `nyc report` part). This is  strictly to keep feature parity (the coverage report of this code is effectively the same as before), but in the near future, we might want to keep both reports separate, for example to continue separating client/server. Another reason would be to use something like Codecov, which I believe has the ability to have multiple reports. This is down the road though, our coverage is not good enough to make hosting them somewhere be useful (I think).

A few extras with this commit:

- Coverage summary is displayed when tests are run (this is not slowing down tests)
- Tests check for leaks (see https://mochajs.org/#--check-leaks)
- Tests now output with the `dot` reporter. This is nice as `npm test` runs in parallel, the whole output holds in a few lines instead of spanning over multiple screens.
2018-02-20 15:32:30 +02:00
Pavel Djundik
f646fbbd4f Add yarn.lock, update CI services to run yarn 2018-02-20 11:28:14 +02:00