You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may have too big an impact on W3C code but I thought I should ask.
We have some tests that are a "should" rather than a "shall", e.g. start-up delay. A "fail" of such a test would be more logical as a "warning" rather than a "fail".
Is "warning" supported by the W3C test runner or is it purely binary, pass / fail?
If the W3C test runner is purely binary, is there any practical way to add "warning" to the reports?
The text was updated successfully, but these errors were encountered:
This may have too big an impact on W3C code but I thought I should ask.
We have some tests that are a "should" rather than a "shall", e.g. start-up delay. A "fail" of such a test would be more logical as a "warning" rather than a "fail".
Is "warning" supported by the W3C test runner or is it purely binary, pass / fail?
If the W3C test runner is purely binary, is there any practical way to add "warning" to the reports?
The text was updated successfully, but these errors were encountered: