-
Notifications
You must be signed in to change notification settings - Fork 667
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
Regression tests for nuclinfo.minor_pair #977
Conversation
|
||
def test_minor_pair_1(self): | ||
val = nuclinfo.minor_pair(self.u, 3, 17, seg1='RNAA', seg2='RNAA') | ||
assert_almost_equal(val, 16.649, decimal=3) |
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.
where do these values come from? Might be useful when the test fails after a refactor.
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.
If it's regression then probably just from running the tests in filling in the values that are needed to make the tests pass.
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.
Yes, that is what I did.
Anyone who sacrifices a few spare minutes for writing tests is a hero! |
Looking good! Can definitely chip away at coverage like this |
* Added two regression tests for MDAnalysis.analysis.nuclinfo.minor_pair * Added CHANGELOG entry for new MDAnalysis.analysis.nuclinfo.minor_pair regression tests.
This PR simply adds two regression tests for
MDAnalysis.analysis.nuclinfo.minor_pair
It is a subset of the additions required for Issue #790. I realize that optimally I might do all of the regression tests and close the issue, but just wanted something relatively simple I could "get done" with a few spare minutes.