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
Make unit test assertions more strict #10
Comments
mahozad
added
bug
Something isn't working
enhancement
Improving an existing feature
labels
Jul 6, 2021
mahozad
added
tests
Related to library tests
and removed
bug
Something isn't working
enhancement
Improving an existing feature
labels
Jul 6, 2021
mahozad
added a commit
that referenced
this issue
Jul 6, 2021
mahozad
added a commit
that referenced
this issue
Jul 6, 2021
mahozad
added a commit
that referenced
this issue
Jul 6, 2021
mahozad
added a commit
that referenced
this issue
Jul 8, 2021
mahozad
added a commit
that referenced
this issue
Jul 8, 2021
mahozad
added a commit
that referenced
this issue
Jul 8, 2021
mahozad
added a commit
that referenced
this issue
Jul 8, 2021
mahozad
added a commit
that referenced
this issue
Jul 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In unit tests that compare floating point numbers, update the assertions to compare with 0.01 precision instead of current 1.
This is because current comparisons may give false negative results, that is, pass when they should have failed.
The text was updated successfully, but these errors were encountered: