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

Treat 501 errors as neither pass nor fail #82

Open
kjetilk opened this issue Jul 26, 2021 · 1 comment
Open

Treat 501 errors as neither pass nor fail #82

kjetilk opened this issue Jul 26, 2021 · 1 comment

Comments

@kjetilk
Copy link

kjetilk commented Jul 26, 2021

Following CommunitySolidServer/CommunitySolidServer#798 I think it makes sense to treat 501 as neither pass nor fail, as it is the server explicitly acknowledging that it knows it hasn't implemented a feature.

Earl doesn't have the exact right predicate for this, as the test has been done, and it applies, it just doesn't count towards the server pass or failure counts.

@edwardsph
Copy link
Collaborator

We have limited outcomes in the EARL vocab so may need to use earl:failed but add rdfs:comment to highlight the distinction. When creating the report assertions we need to check the status or responseStatus for 501

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

2 participants