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

Covering normative statements via testcases #4

Open
OR13 opened this issue Aug 16, 2023 · 0 comments
Open

Covering normative statements via testcases #4

OR13 opened this issue Aug 16, 2023 · 0 comments

Comments

@OR13
Copy link
Collaborator

OR13 commented Aug 16, 2023

Test cases will cover normative statements, for example:

typ and cty values are easy to test, since they appear in header parameters.

However there are some tricky cases that require full verification... for example:

schema credentials and status credentials.

we'll need negative cases for those, and we might want to encode specific error messages, that some implementers might make use of and others might ignore.

Here are a few examples:

  • Failed to verify credential status, could not dereference status list
  • Failed to verify credential status, signature verification failed.
  • Failed to verify credential status, could not dereference public key.
  • Failed to verify credential status, status list no longer valid (expiration in the past)
  • Failed to verify credential status, status list not yet valid (activation in the future)

I would like for use to encode some of these errors in test cases, even if a "pass" for the test case is simply raising a generic "error" flag.

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

No branches or pull requests

1 participant