Add test setup

[dignifiedquire]

Every decent (software) project needs tests

"Frontend" (browser processes)

This is about testing react components in isolation. To run the tests we should use karma and spawn a chrome process (close enough to electrons chromium instances). Interesting modules and notes

• https://github.com/sheepsteak/react-shallow-testutils
• https://github.com/percyhanna/rquery
• https://github.com/jhnns/rewire-webpack (mock require calls, especially ipc)
• https://github.com/pgte/nock (mock http calls)

"Backend" (electron main process)

This is much harder, as too much functionality depends on running the real deal aka an electron instance. So very happy to hear any suggestions around this.

[hacdias]

Spectron --> https://github.com/electron/spectron

[hacdias]

State of the thing: Taking this branch as the state from which we should start writing tests, we've got many different components to test:

• components which Simple React components which seem to be relatively easy to test
• controls which are subdivided in two:
  • main process handlers.
  • renderer process handlers.
• panes which are a bit more complex React Components that can use Electron's API directly.
• utils some simple... utils? Easy to test.
• views main entry points for the pages Welcome and Menubar.
• index.js, errors.js, config.js

I can easily start to create the tests for the components and the utils. Although, I'm not sure how to do testing for the controls, which are basically event handlers of ipcMain and some other general stuff. Nor for panes and views.

[olizilla]

WIP on adding spectron test in #730

[hacdias]

Superseded by #1121