automated tests / CI improvements

[OriHoch]

TODO

• currently we have travis run multiple python versions, need to determine if the versions it's running are ok (I think we need to add python 3.6)
• should update to use tox
• should remove the tests from the published package
• should run the tests using standard test runner (e.g. pytest or python -m unittest)
• should have automatic publishing to pypi when github release is published. something like this - https://github.com/hasadna/knesset-data-python/blob/master/.travis/after_success.sh

[OriHoch]

could split this issue into sub-issues for each bullet..

[ninjaaron]

I'm pretty much a newb when it comes to CI anything, so I'll have to read up about Travis and Tox when I get the time. As far as 3.6, that along with 2.7 are the only python versions I have locally, so I'm sure to know when they don't work!

Whenever I get to reading about Travis and tox, I'll let you know if I have any ideas, but keep me posted if you need me to do something before that.

[ninjaaron]

I'll work on moving the tests out of the package and getting them to run with python -m unittest. Low hanging fruit. 😉