Due to the relatively-high activity on this repo, I'm putting down one of my larger goals in hopes that maybe people will help chip in on this!
I'm looking to rise the total repo testing percentage up to 97+% from the current 89% (I'll consider this issue closed at 97%).
For those just starting out with this, here's a few pointers:
- Take a look at the Coveralls report on the master branch. You can click on individual files after expanding the repo "Tree" on this page.
- Each source file will show green or red if a test covers a line of code. Of course, less red is better - and adding tests to our test suite will help make those "red" lines of code into "green" ones :)
- The test suite can be found here. You can put new tests in either the respective ipynb file or the PyTest files. You should always try to instrument the test using the PyTest file first - but if the output of a function is a graph or something that isn't easily testable by using assert statements, you can put it in the ipynb file.
Last thing, please try to make as many individual PRs on this as possible - only group test changes into the same PR if they're pertaining to the same function/functionality. Otherwise, create separate PRs for all new changes, please!
Thanks to all the new contributors to this repo - we appreciate your help!
Due to the relatively-high activity on this repo, I'm putting down one of my larger goals in hopes that maybe people will help chip in on this!
I'm looking to rise the total repo testing percentage up to 97+% from the current 89% (I'll consider this issue closed at 97%).
For those just starting out with this, here's a few pointers:
Last thing, please try to make as many individual PRs on this as possible - only group test changes into the same PR if they're pertaining to the same function/functionality. Otherwise, create separate PRs for all new changes, please!
Thanks to all the new contributors to this repo - we appreciate your help!