W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2011

[Bug 11813] Clarification request for the Constr-cont-nsmode-5 test

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Feb 2011 14:48:18 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PpMCQ-0005UB-EV@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11813

--- Comment #6 from Michael Kay <mike@saxonica.com> 2011-02-15 14:48:17 UTC ---
The source document "atomic.xml" is used by the following tests:


fn-union-node-args-015 to 022
fn-intersect-node-args-015 to 022
fn-except-node-args-015 to 021

Constr-cont-constrmod-1 to 8
Constr-cont-nsmode-5 to 10
Constr-compelem-compname-8
Constr-compattr-compname-8
Constr-docnode-constrmod-1 to 4
Constr-comppi-compname-8 to 9
Constr-compelem-constrmod-1, 2, 5, 6

casthcds1 to 42
schema-import-4 to 31

The first three groups don't seem to care whether the input is typed or
untyped, the result will be the same either way.

The last two groups are positioned within the SchemaImport part of the test
group hierarchy.

So the problems are confined to the (appallingly named) Constr- groups.

Some of these appear to have alternate results. In some cases the alternate
results appear to be tagged 'input-document="typed"' or
'input-document="untyped"' In fact, the only tests that use this attribute are

Constr-cont-constrmod-4
Constr-cont-constrmod-8
Constr-cont-nsmode-5
Constr-cont-nsmode-6
Constr-cont-nsmode-7
Constr-cont-nsmode-8
Constr-compelem-constrmod-8

which is (almost) a subset of the tests listed above.

The following query retrieves all tests whose source documents have a schema:

declare namespace c='http://www.w3.org/2005/02/query-test-XQTSCatalog';
//c:test-case[c:input-file=/*/c:sources/c:source[@schema]/@ID]/<t
group='{string-join(ancestor::c:test-group/c:GroupInfo/c:title, '/')}'
file='{string(c:input-file)}'>{@name}</t>

Most of these, but by no means all, are in the "Optional Features" part of the
catalog. Among those in the Minimal Conformance section are ForExprTypeNNN and
orderByNNN (source document orderData), LocalNameFromQNameFuncNNN and
namespaceURIFromQNameFuncNNN (source document QNameSource), and the three
CatalogNNN tests.

The ForExprTypeNNN tests have been split into two groups: where the results
depend on schema validation they have been moved into the "Schema Import" group
(even if they do not import a schema); in other cases they have been left in
the "Minimal Conformance" group.

For the NamespaceURIFromQName and LocalNameFromQName tests, a different
strategy has been employed again: although these tests were clearly originally
written to use typed input, they have been modified to cast the typed input to
a string so that they no longer depend on schema validation (and, as a
side-effect, no longer test what they were designed to test).

Proposal: follow the crowd. In future, tests that depend on schema-validating
the input should go in the "Schema Import" group. Tests that currently have two
results for the two cases should be split into two tests. Scrap the
almost-unused @input-document='typed|untyped' attribute which appears to have
been an earlier attempt to solve this problem.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 15 February 2011 14:48:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:45 UTC