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

Communicate "why it matters" on each testcase #161

Open
woodruffw opened this issue Jan 3, 2024 · 2 comments
Open

Communicate "why it matters" on each testcase #161

woodruffw opened this issue Jan 3, 2024 · 2 comments
Assignees

Comments

@woodruffw
Copy link
Collaborator

Pointed out by @reaperhulk: the current metadata for each testcase communicates whether it passes or fails, but doesn't adequately communicate why or how severe a disagreeing result would be.

We should figure out some way to communicate that, e.g. "failing this testcase means that an implementation is likely to accept certificates for unintended domains."

@woodruffw
Copy link
Collaborator Author

Thinking a little more about this: we could probably have a Severity enumeration that defaults to UNDETERMINED, and goes UNDETERMINED, LOW, MEDIUM, HIGH, CRITICAL.

@woodruffw
Copy link
Collaborator Author

#236 adds the Importance model and qualifier to each testcase. Leaving this open for the actual fill-in.

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