Restore 100% unit test coverage - #141

cc @jaitaiwan I think we should fold this into our CI work. Not sure if tox is needed for that work, but I'd like to get the test coverage and other fixes in.

I'd like to see this folded into the CI stuff although Travis already provides multiple CI python versions... unless tox does this differently somehow?

FWIW, the key feature of tox is that it allows the developer to run the tests locally before pusing (assuming she has the appropriate Python versions available). Travis can then be used to drive tox. For instance, see:

• https://github.com/GoogleCloudPlatform/gcloud-python/blob/master/.travis.yml
• https://github.com/zopefoundation/zope.component/blob/master/.travis.yml

Merged w/ master and fixed test failures due to hash randomization.

@jaitaiwan the main thing you get with tox, as @tseaver mentioned, is being able to run tests against multiple versions of Python locally. Travis does this on PR. I propose we split this into two PRs, get the test coverage merged in, and then move the tox discussion to a 2.0 thread.

👍

@tseaver reckon you could open a new PR against master instead?

@joestump I merged with master yesterday, and added a couple of test fixes.

Ugh sorry @tseaver I meant develop instead of master.