Skip to content
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

Update ZKP tests for changes in VC Data Model v1.1 #127

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from

Conversation

clehner
Copy link
Member

@clehner clehner commented Feb 3, 2022

Update the test suite to correspond with changes in w3c/vc-data-model#818 to normatives statements about ZKPs.

  • Remove requirement for credentialSchema
  • Remove requirement for verifiable presentation proof
  • Add skipped test for credential definition
  • Add skipped test about derived verifiable credential

I added the skipped tests as I am not sure how to test those.
Possibly the one about credentialSchema could be addressed with a new optional section to test ZKP types that require credentialSchema. But there is already a section testing credentialSchema.
Several tests related to credentialSchema are removed from the ZKP section, but similar tests are still present in the credentialSchema section (test/vc-data-model-1.0/20-schema.js).

The requirement that a verifiable credential "MUST contain all information necessary to verify..." could perhaps be tested with a contrived example where the signature input contains some data not present in the verifiable credential. But I don't know if that is representable in the VC Data Model.

- Remove requirement for credentialSchema
- Remove requirement for verifiable presentation proof
- Add skipped test for credential definition
- Add skipped test about derived verifiable credential
@iherman
Copy link
Member

iherman commented Feb 9, 2022

The issue was discussed in a meeting on 2022-02-09

  • no resolutions were taken
View the transcript

4.1. [Tracking Issue - Proposed Corrections Feedback] Test suite improvements are needed (issue vc-test-suite#126)

See github issue vc-test-suite#126.

Charles Lehner: Tallted has commented on this.

Charles Lehner: See Ted's comments.

See github pull request vc-test-suite#123.

Charles Lehner: when a test has not been evaluated or when feature did not previously exist, I still need to respond to TallTed.

See github pull request vc-test-suite#127.

Brent Zundel: is there anyone on the call that can review these?.

Manu Sporny: you can add me.
… we did not copy 1.0 test suite to a new one. Instead we should add tests to the 1.0 test suite.
… this will not require testers to re-run all their previous tests.
… there will be a proposal to change the way we run tests for v2.0.

it.skip('credential definition MUST be defined in credentialSchema', async function() {
/*If a credential definition is being used, the credential
definition MUST be defined in the credentialSchema property,
so that it can be used by all parties to perform various cryptographic
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
so that it can be used by all parties to perform various cryptographic
so all parties can use it to perform various cryptographic

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@clehner -- If #127 (comment) is asking me about the above rephrasing, then I would definitely change it here, and if such editorial change can still be made in the other doc, then I would change it there as well.

@clehner
Copy link
Member Author

clehner commented Feb 9, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants