Improve unit test runner

[abshinn]

Make use of unittests' TestSuite class for running unit tests. This will make it easier to measure test coverage.

[mikofski]

I recommend using pytest to autodiscover all of your tests, even Python unittest.TestCase. Then you can remove the install: pip install . and just have install pip install -r $REQ_FILE in .travis.yml and you can remove run_test as well. Also consider maybe moving your tests folder into the rdtools package, and making rdtools.tests a package. See my post on recommended project layout - note, there are many styles, and your current layout is fine.

[abshinn]

Fixed in PR #81.

[mdeceglie]

I suggest keeping issues open until they are fixed in a release. One they are fixed in the development branch we can add the label "Fixed in development branch" until they are incorporated in a new release.

[mikofski]

If you put the words "fixes/closes #issue" in the commit message or in the PR main comment then when the commit/PR is merged to master (or the default branch), the issue will close automatically.

See https://help.github.com/articles/closing-issues-using-keywords/

When a pull request or commit references a keyword and issue number, it creates an association between the pull request and the issue. When the pull request is merged into your repository's default branch
, the corresponding issue is automatically closed.

[abshinn]

@mdeceglie Ah, makes sense. If people run into a problem in master, they can see whether or not it has already been fixed in development.