-
Couldn't load subscription status.
- Fork 305
Rearrange tests for XOnlyPublicKey::from_slice
#785
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
Rearrange tests for XOnlyPublicKey::from_slice
#785
Conversation
|
The CI failures are because when you compile with I think the best solution is to add these tests as a new unit test with |
|
Actually, I just saw that there is a |
…st_pubkey_from_slice
|
I did the slight refactor (without deleting any test) - feel free to merge or close as you please. |
XOnlyPublicKey::from_sliceXOnlyPublicKey::from_slice
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.
ACK a4cb345; successfully ran local tests; yeah, sure. I think this makes the tests a bit easier to follow
…icKey::from_slice`
a4cb34500884721d74ce9c0111fa9ad695ed889e Reposition test_pubkey_from_bad_slice, and move failing cases from test_pubkey_from_slice (Salvatore Ingala)
Pull request description:
Adds two test cases for parsing an invalid key (despite it being 32-byte long).
Perhaps the test for `ZERO` is redundant, as `7` also has no square root, but it felt natural to add it anyway.
ACKs for top commit:
apoelstra:
ACK a4cb34500884721d74ce9c0111fa9ad695ed889e; successfully ran local tests; yeah, sure. I think this makes the tests a bit easier to follow
Tree-SHA512: f5f7f3c175c65bd9f1bb589e18246c9155d8cbed2f43ff425757222cb64fe2ec6b0e793cef500ff3e20d33135c7065fe5a835c3f4693d1b801f71fe36db25a8d
…icKey::from_slice`
a4cb34500884721d74ce9c0111fa9ad695ed889e Reposition test_pubkey_from_bad_slice, and move failing cases from test_pubkey_from_slice (Salvatore Ingala)
Pull request description:
Adds two test cases for parsing an invalid key (despite it being 32-byte long).
Perhaps the test for `ZERO` is redundant, as `7` also has no square root, but it felt natural to add it anyway.
ACKs for top commit:
apoelstra:
ACK a4cb34500884721d74ce9c0111fa9ad695ed889e; successfully ran local tests; yeah, sure. I think this makes the tests a bit easier to follow
Tree-SHA512: f5f7f3c175c65bd9f1bb589e18246c9155d8cbed2f43ff425757222cb64fe2ec6b0e793cef500ff3e20d33135c7065fe5a835c3f4693d1b801f71fe36db25a8d
Adds two test cases for parsing an invalid key (despite it being 32-byte long).
Perhaps the test for
ZEROis redundant, as7also has no square root, but it felt natural to add it anyway.