test coverage for parse_hex_string()
#641
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arvidn
force-pushed
the
parse_hex_string-test
branch
2 times, most recently
from
7a05d00
to
a799b19
Compare
Pull Request Test Coverage Report for Build 10248750986Details
💛 - Coveralls |
arvidn
force-pushed
the
parse_hex_string-test
branch
from
a799b19
to
60ac4ae
Compare
…ure and PrivateKey). Add test cases to python tests
arvidn
force-pushed
the
parse_hex_string-test
branch
from
60ac4ae
to
93879e1
Compare
arvidn
commented
Aug 5, 2024
Rigidity
approved these changes
Aug 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
make GTElement also use parse_hex_string (just like PublicKey, Signature and PrivateKey).
Add test cases to python tests.