Add new valid test vectors for participant - #148
Draft
DarkWindman wants to merge 3 commits into
Draft
Conversation
Contributor
Author
|
It's just a draft for now. I think we can expand on it further |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR partially addresses #138 by expanding valid test-vector coverage for participant functions.
Changes:
Per-idx valid cases for
participant_step1,participant_step2, andparticipant_finalize. Previously each group had a single valid case foridx=0; now there is one valid case per participant index in the group.Additional aux_rand pattern for
participant_step2: a valid case withauxRand = 0x00...00Test harness extension (
tests.py): valid test cases now support per-case overrides forhostseckey,random, andauxRand