-
Notifications
You must be signed in to change notification settings - Fork 6
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
WIP - Test cases for base64 module #15
Conversation
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.
Nice work @akash-suresh, this is a great start 😁
I think you've got the fundamentals down pat, so the comments below are about how we can take it to the next level.
Thanks @Zac-HD 😄. I shall look at the comments and make changes accordingly. |
- Added arguments casefold, map01 to b32decode - Added arguments casefold to b16encode & b16decode - Updated wrapcol argument strategy of a85encode to take 0 more often. - Added argument pad to a85encode & a85decode - Added argument pad to b85encode & b85decode - Fixed usage of pad argument in a85decode & b85decode, by manually adding padding when len(payload)!=4
Thanks @akash-suresh! If you're still interested in writing |
Thanks for merging @Zac-HD . This is my first open source contribution 👻 . I have already started on writing tests for |
Congratulations! |
Cross-reference: HypothesisWorks/hypothesis#2430 |
@Zac-HD I have made an attempt to add a few test cases for the
base64
module.I had a doubt - This particular test case
test_b85_encode_with_padding_decode_round_trip
, is failing forpayload = b'\x00'
. I setpad = True
whileb85encode
. The expectation is thatb85decode
, will implicitly remove the padding, but it fails to decode. Let me know your thoughts.