Add testing suite to client

[mstenta]

While this project is still pretty new, I think it would be worth making automated testing a core part of the development process. This is something I wish I had done more of with farmOS itself (although farmOS sits on top of a lot of underlying components that have automated tests already), and I hope to make it a key part of the Drupal 8 upgrade initiative.

I see that Vue.js provides some tooling for this: https://vuejs.org/v2/guide/unit-testing.html

Perhaps we can get TravisCI set up with this repo, write some tests for the code we have thusfar, and then make it a part of the process moving forward (along with documentation).

What do you think?

[jgaehring]

Absolutely! 💯

This has crossed my mind several times, especially in #19 where I mentioned the possibility of inadvertently breaking the code-base by removing farmos-client from farmos-native's list of dependencies. It also strikes me as particularly useful now that we have the native and client repos broken into a separate packages; it would be nice to know each works independently.

I'll look more into Vue's recommendations, as you referenced above. For the client, which no longer has it's own Webpack or other devDependencies, it might make more sense to just use Karma (or Jest or whatever) with some npm scripts for local testing, with TravisCI for some extra safety at the repository level.

It might also make sense to work on the basic setup for this in tangent with #1 (linting).

More food for thought... There a lot of console.log()statements still in the code that ideally shouldn't go into production, a lot of which I've already removed, but they might actually work as useful sign-posts for where we need to write a test.

[mstenta]

(Transferring all issues from old repository. See #92)