W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2007

[Bug 4024] ST-WhereExpr001 should not be expected to fail?

From: <bugzilla@wiggum.w3.org>
Date: Thu, 13 Sep 2007 07:40:20 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1IVjJE-00060G-Kq@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4024





------- Comment #10 from frans.englich@telia.com  2007-09-13 07:40 -------
I agree that the documentation doesn't say that tests in the "Optional
Features" group mustn't be run. Have a look at:

http://www.w3.org/XML/Query/test-suite/XQTSReportSimple.html

For several of the optional features the fields are white, meaning they are
untested for that implementation. For instance, the implementation BaseX hasn't
run the tests for Schema Import Feature, and Anglo doesn't support the Static
Typing Feature.

The optional feature-tests are designed for testing those optional features, so
if one doesn't implement it, they will obviously fail. For instance,
Constr-compelem-constrmod-1 doesn't allow XQST0009, which an implementation
that doesn't support Schema Validation, will raise.

Same goes for ST-WhereExpr001. An implementation implementing the static typing
feature, must raise FORG0006, and that's what the test tests.

For my own driver I do this by letting the code that reads the catalog file,
skip the whole sub-tree if a category is encountered whose name is a category
Patternist doesn't support.
Received on Thursday, 13 September 2007 07:40:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 December 2014 19:59:37 UTC