Set up Continuous Integration and Unit Test Framework #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From looking at some of the activity in the issues (#10, #11, #12), it sounds like there is interest in adding and expanding some of the features and functionality of RivGraph. I have some things I will likely need to add to the package as well. One of the 'task list' items is also to implement unit testing.
To help start all of that off, I thought it would be useful to get the package set up for continuous integration to ensure that proposed changes do not break the package. This pull request implements continuous integration via Travis CI, and provides the framework for automated unit testing and code coverage (could be done via Coveralls). An example "dummy" unit test is currently in the /tests folder as an example of how the file should be formatted.
Currently, the Travis set-up tests and successfully installs the package in Python 3.7 and 3.8. Note to @jonschwenk, after merging this pull request you should be able to add the badge to the Readme if you want.