- From: <bugzilla@jessica.w3.org>
- Date: Wed, 10 Jul 2013 14:45:24 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22423 --- Comment #1 from O'Neil Delpratt <oneil@saxonica.com> --- We think the reporting is consistent with the categories in the schema. In the schema for notRun it states: "Indicates that the test was not run for unspecified reasons, perhaps because the test uses a feature that is not yet implemented in the product under test. For statistical purposes this outcome is treated in the same way as "fail". This is the default outcome assumed for tests that are present in the test catalog on the date of the test run, but which are not present in the results submission." It seems that in the situation you are describing it would be more appropriate to use 'n/a' meaning the test is not applicable to your product. The following sentence needs to be changed: "An implementation that cannot set the context as required should behave in the same way as if a dependency has not been satisfied, ideally reporting the test as "notRun" with a reason." Here we need to change 'notRun' to 'n/a'. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 10 July 2013 14:45:31 UTC