-
Notifications
You must be signed in to change notification settings - Fork 518
Test: Use NearZeros to make simple Equal() tests #6458
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
Conversation
NeasrZeros had to be improved to avoid looping on recursive types. But it's now easy to write easy Equal() tests that will fail if you add a field to a type and forget to modify Equal(). Caught a bug in EvalDelta.Equal().
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6458 +/- ##
==========================================
- Coverage 50.90% 50.73% -0.17%
==========================================
Files 665 658 -7
Lines 111546 111459 -87
==========================================
- Hits 56780 56554 -226
- Misses 51899 52034 +135
- Partials 2867 2871 +4 ☔ View full report in Codecov by Sentry. |
cce
left a comment
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.
there is also
- verify.GroupContext
- crypto.MultisigSig
and that's it for Equal AFAIK
…)" This reverts commit d1da52e.
NearZeros had to be improved to avoid looping on recursive types. But it's now easy to write easy Equal() tests that will fail if you add a field to a type and forget to modify Equal(). Caught a bug in EvalDelta.Equal().
Summary
Test Plan