Testing infrastructure

[chris-erickson]

• Adds support for pytest
• Adds CircleCI for continuous integration testing
• Adds Coveralls for code coverage reporting (doesn't run unless tests pass, but this is not made clear anywhere)
• Adds Code Climate for checking the "quality" of the code. This actually requires no integration code-side, just setting up an account at codeclimate.com
• Adds a build status badges in the README
• Fixes some things like project naming
• Comments out some test code, which should be removed once it's confirmed that's correct. This really needs to be removed or addressed, but it's just too early to do so.

The result of these is a couple status checks at the end of the pull request. This doesn't add immediate value to the code but over the years I have found that these checks can provide valuable insight and encouragement to get the code right. Countless times I and others have said I'll come back and fix this soon, never again to return.

On the project homepage we get:

Part of this project is building a "test" Django project so that I can develop on the JSON feed, and use it the way a typical user would (pip install, etc). Eventually will likely need a sample project for tests, which could also help illustrate how to use the tool.

One small point - I'll be doing a squash and merge for most PR's. This one is particularly fitting, as it won't load the master branch with 15 garbage commits where I was fighting with the CI system. The result will be a single merge commit with all 15 collapsed into it.

Resolves #5 and resolves #6