26861 2014-09-19 15:17:14 +0000 parse-xml-fragment-022 should allow error XPST0005 2014-11-18 23:51:39 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Working drafts PC All RESOLVED FIXED P2 normal --- 1 josh.spiegel oneil mike public-qt-comments oldest_to_newest 111805 0 josh.spiegel 2014-09-19 15:17:14 +0000 <test-case name="parse-xml-fragment-022" xmlns="http://www.w3.org/2010/09/qt-fots-catalog"> <description>parse-xml-fragment test - result is parentless</description> <created by="Michael Kay, Saxonica" on="2013-01-07"/> <environment name="empty"/> <test><![CDATA[parse-xml-fragment("<a/>")/..]]></test> <result> <assert-empty/> </result> </test-case> This test should also allow XPST0005 (During the analysis phase, it is a static error if the static type assigned to an expression other than the expression () or data(()) is empty-sequence()). The return type of parse-xml-fragment is document-node()?. 114923 1 mike 2014-11-14 09:38:06 +0000 Technically you should create two versions of the test, with dependencies on static type checking being enabled/disabled, and different results for the two cases, rather than simply defining two permitted results. 114934 2 josh.spiegel 2014-11-14 15:41:28 +0000 At the very least, there seems to be a strong precedent for allowing XPST0005 in such cases without tagging the test with the static typing feature. Bug 21620 is one example but there appear to be many cases throughout the test suite. I think in this case we should keep with the precedent and simply add the alternate result. 114936 3 mike 2014-11-14 15:51:02 +0000 The precedent is there because many of the tests were written before we had the ability to define fine-grained dependencies. Adding an error as a possible result is that it makes it very easy for test failures to go unnoticed, since generating the wrong error code is not something that gets reported as a test failure. 115081 4 josh.spiegel 2014-11-18 23:51:39 +0000 Applied fix suggested in Comment 1.