-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds unit tests #41
Adds unit tests #41
Conversation
* also makes some minor docstring changes to datatypes * also updates some dependencies
* also updates docstrings in datatypes
updates unit tests after deletion of old interface
New Interface for Factor Graph Model Building (#53)
* ci now uses pytest-cov to generate reports * removes coverage requirement from poetry dev reqs * small update to codecov yml
Merging after heretic model incorporation
* gets 100% coverage for nodes.py * updates poetry to depend on strictly python 3.7 (others cause problems with pre-commit, etc.) * minor update to gitignore
* updates ci to run correct testing command * suppresses coverage checking for certain functions that cannot possibly be run (in groups.py)
Coverage is now 100% - ready for review and potential merging! Note that I had to tell |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One major comment: instead of relying on manual annotation for lines we should ignore in coverage calculation, let's replace pass
with docstrings and ignore NotImplementedError
lines.
Also made various minor comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after addressing a few more minor comments
Co-authored-by: Guangyao Zhou <[email protected]>
Includes 1 E2E test, as well as a few files with basic tests for some of our other functionalities. These other tests are incomplete and intended to show a proposal for how we might structure all our test files. Would love to get feedback on (1) test structuring and (2) which files/functions we should create tests for, and which ones will just be unnecessary
Resolves #11