-
Notifications
You must be signed in to change notification settings - Fork 9
Add test vectors for mocked classes #76
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
base: main
Are you sure you want to change the base?
Conversation
ping @dlongley @msporny @dmitrizagidulin trying to add test vector generation code to this code base, before attempting to reimplement the client for the SDS. |
partially blocked by digitalbazaar/http-signature-zcap-invoke#11 |
@OR13, ack, we're looking into the partial blocker. |
This can be merged, and I can circle back to add better tests for http invocation if thats desirable. |
@aljones15 -- we need to run these test vectors against our current implementations to see if everything checks out. If it does, we can merge this -- if not, we should see what needs to be tweaked (one way or the other). I don't want to push test vectors forward that cause more people to have bugs/differences that shouldn't be there. |
Co-authored-by: Dave Longley <[email protected]>
any movement on this? |
In order to establish test vectors for EDVs we need to extract the string values from the mocked classes, and the expected inputs and outputs associated with hmac and ed25519 sign.
This PR adds JSON files for establishing conformance for mocked classes.