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?
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?