13133 2011-07-04 18:39:36 +0000 Tests that do not specify results for XQuery 3.0 2016-04-12 13:54:08 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite 1.0.3 PC Windows 3.1 RESOLVED MOVED P2 normal --- 1 spungi benjie.nguyen mike oneil public-qt-comments oldest_to_newest 50646 0 spungi 2011-07-04 18:39:36 +0000 There are a bunch of tests that have as expected result an error not marked as being valid *only* for XQuery 1.0. Also these tests do not state the behavior for XQuery 3.0. 1) K2-FunctionCallExpr-6: - add  spec-version="1.0" for the XPST0017 - add XPTY0004 as alternate result because xs:string can not be treated as xs:anyNode like the F&O spec expects: http://www.w3.org/TR/2011/WD-xpath-functions-30-20110614/#func-generate-id 2)K2-FunctionCallExpr-7 - add  spec-version="1.0" for the XPST0017 - add  result for XQuery 3.0 3)K-DataFunc-1 - add  spec-version="1.0" for the XPST0017 - add  result for XQuery 3.0 4)K2-DataFunc-1 - add  spec-version="1.0" for the XPST0017 - add  result for XQuery 3.0 5)K-DocumentURIFunc-2 - add  spec-version="1.0" for the XPST0017 - add  result for XQuery 3.0 6)K-NodeNameFunc-1 - add  spec-version="1.0" for the XPST0017 - add  result for XQuery 3.0 50901 1 spungi 2011-07-11 13:39:05 +0000 The same is true for test K-DocumentURIFunc-2: Here is what's stated in cat/DocumentURIFunc.xml <test-case is-XPath2="true" Creator="Frans Englich" name="K-DocumentURIFunc-2" FilePath="Functions/AccessorFunc/DocumentURIFunc/" scenario="runtime-error"> <description>A test whose essence is: `document-uri()`.</description> <query name="K-DocumentURIFunc-2" date="2007-11-26+01:00"/> <input-file role="principal-data" variable="input-context">emptydoc</input-file> <expected-error>XPST0017</expected-error> </test-case> And here is the F&O Spec 3.0: http://www.w3.org/TR/xpath-functions-30/#func-document-uri 50906 2 spungi 2011-07-11 14:12:14 +0000 Same applies for test http://dev.w3.org/cvsweb/~checkout~/2006/xquery-test-suite/TestSuiteStagingArea/Queries/XQuery/Expressions/Construct/ComputeCon/ComputeConComment/Constr-compcomment-dash-4.xq and http://dev.w3.org/cvsweb/~checkout~/2006/xquery-test-suite/TestSuiteStagingArea/Queries/XQuery/Expressions/Construct/ComputeCon/ComputeConComment/Constr-compcomment-doubledash-4.xq That do not have an alternate result stated for XQuery 3.0 89695 3 mike 2013-06-21 13:54:54 +0000 I have reviewed these tests and in each case there is an existing test in QT3 that adequately tests the equivalent construct in XQuery 3.0. For example K2-FunctionCallExpr-6 tests what happens when a non-node is supplied to generate-id(); for XQuery 3.0 this is tested by generate-id-903. No changes needed. 89697 4 mike 2013-06-21 14:17:56 +0000 Sorry the previous comment should have been against bug 22333 (the QT3 equivalent bug) 125825 5 oneil 2016-04-12 13:54:08 +0000 I am closing this bug issue as it has been transferred to the QT3 test suite bug list: See bug #22333.