Skip to content

Issues: w3c-ccg/data-integrity-test-suite-assertion

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.

Sign up for GitHub

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

22 Open 8 Closed
22 Open 8 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Add test vectors that use i18n strings
#83 opened Jul 21, 2024 by msporny
Add vpVerifiers for domain & challenge.
#82 opened Jul 21, 2024 by aljones15
Verification Tests
#76 opened Jul 16, 2024 by aljones15
@aljones15
Add "If options has a non-null challenge item, it MUST be equal to proof.challenge or an error MUST be raised and SHOULD convey an error type of PROOF_GENERATION_ERROR."
#75 opened Jul 16, 2024 by aljones15
@aljones15
Add "If options has a non-null domain item, it MUST be equal to proof.domain or an error MUST be raised and SHOULD convey an error type of PROOF_GENERATION_ERROR."
#74 opened Jul 16, 2024 by aljones15
@aljones15
Add "If one or more of the proof.type, proof.verificationMethod, and proof.proofPurpose values is not set, an error MUST be raised and SHOULD convey an error type of PROOF_GENERATION_ERROR."
#73 opened Jul 16, 2024 by aljones15
@PatStLouis
Add "Let proof be the result of calling the createProof algorithm specified in cryptosuite.createProof with unsecuredDocument and options passed as a parameters. If the algorithm produces an error, the error MUST be propagated and SHOULD convey the error type."
#72 opened Jul 16, 2024 by aljones15
@PatStLouis
Add: "Cryptographic suite designers MUST use mandatory proof value properties defined in Section 2.1 Proofs, and MAY define other properties specific to their cryptographic suite."
#71 opened Jul 16, 2024 by aljones15
@PatStLouis
nonce test
#68 opened Jul 16, 2024 by aljones15
@PatStLouis
proof chain tests
#67 opened Jul 16, 2024 by aljones15
@PatStLouis
2
assert on verificationMethod "contents of the value MUST be expressed with a header and encoding"
#66 opened Jul 16, 2024 by aljones15
2 tasks
Consider tests that perform input context validation
#65 opened Jul 16, 2024 by msporny
Ensure tests exist that fail for inputs that have undefined terms and / or relative URLs
#56 opened Jul 12, 2024 by dlongley
@aljones15
Use camelCase naming in the future
#55 opened Jul 1, 2024 by aljones15
@BigBlueHat @aljones15 @tminard
Create a MockDataIntegrityProof Class
#47 opened Jun 18, 2024 by aljones15
@aljones15 @tminard
test suite mock should use a valid issuer and verifier bug Something isn't working
#36 opened May 17, 2024 by aljones15
@aljones15
statements around created need to be updated
#31 opened Mar 29, 2024 by aljones15
@aljones15
"proof.verificationMethod" field MUST exist and be a valid URL.
#30 opened Mar 29, 2024 by aljones15
@aljones15 @tminard
Ability to pass a context file along in the VC generator
#26 opened Jan 18, 2024 by brianorwhatever
@aljones15
Write tests for the normative statements under section 2.3 Controller Documents in the spec
#20 opened Oct 31, 2023 by JSAssassin
Determine how to test for properties data integrity when VC might contain multiple proofs conforming to another spec enhancement New feature or request
#8 opened May 21, 2022 by aljones15
4 tasks
@aljones15
Test Suite failure causes other Describe blocks in parent test suite to stop
#3 opened Apr 14, 2022 by aljones15
@aljones15
ProTip! Adding no:label will show everything without a label.