- From: <bugzilla@jessica.w3.org>
- Date: Tue, 31 Mar 2015 03:04:13 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21910 Abel Braaksma <abel.braaksma@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Query used: /(xsl:stylesheet|xsl:transform)/@version [not(normalize-space(.) = ('1.0', '2.0', '3.0'))] I found 38 items with a version not in (1.0, 2.0, 3.0), of which 15 where in the version test-set, 4 in backwards, 4 in errors, 1 in use-when (all deliberate) That leaves: * 5 times 1.1 - bug-3102.xsl -> changed to 2.0 - expression-0801.xsl -> changed to 2.0 - expression-0802.xsl -> changed to 2.0 - expression-0803.xsl -> changed to 2.0 - axes-049.xsl -> changed to 1.0 * 1 time 20 - key-050.xsl -> changed to 1.0 * 8 times 2.1 - streamable-065.xsl -> changed to 3.0 - streamable-118.xsl -> changed to 3.0 - streamable-121.xsl -> changed to 3.0 - streamable-122.xsl -> changed to 3.0 - streamable-123.xsl -> changed to 3.0 - streamable-125.xsl -> changed to 3.0 - streamable-128.xsl -> changed to 3.0 Next query used (1.0): /cat:test-set/cat:test-case [cat:dependencies/cat:spec/@value[contains(., 'XSLT10')]] /cat:test/cat:stylesheet /doc(@file)/(xsl:stylesheet|xsl:transform) /@version[normalize-space(.) != '1.0'] Resulting 1703, of which only 8 items where deliberately wrong, and the 1630 others had version 2.0. Next query used (2.0): /cat:test-set/cat:test-case [cat:dependencies/cat:spec/@value[contains(., 'XSLT20')]] /cat:test/cat:stylesheet /doc(@file)/(xsl:stylesheet|xsl:transform) /@version[normalize-space(.) != '2.0'] Resulting in 111 items of which roughly half seems to be in error (1.0 where 2.0 is expected because not testing backwards compatibility or 1.0 behavior) Next query used (3.0): /cat:test-set/cat:test-case [cat:dependencies/cat:spec/@value = 'XSLT30+'] /cat:test/cat:stylesheet /doc(@file)/(xsl:stylesheet|xsl:transform) /@version[normalize-space(.) != '3.0'] Result is 80 items, with at least 2 of them deliberate. I have at this moment only fixed the 14 items mentioned in the beginning that were seriously wrong (though I doubt it influences any test results). Still thinking about fixing the others and whether or not that is actually a good idea. I am uncertain about the many 1.0 tests that have version 2.0, because they may have been changed deliberately in this way, to allow them as 2.0 tests without them behaving in XPath 1.0 compatibility mode. When run with XSLT 1.0, and if no 2.0 features are used, this should not hamper anyone using the test suite to test an XSLT 1.0 processor. I think it does make sense to align the other tests. These are not too many. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 31 March 2015 03:04:15 UTC