[Bug 26861] New: parse-xml-fragment-022 should allow error XPST0005

Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 26861] New: parse-xml-fragment-022 should allow error XPST0005

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26861

            Bug ID: 26861
           Summary: parse-xml-fragment-022 should allow error XPST0005
           Product: XML Query Test Suite
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XML Query Test Suite
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

<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()?.

--
You are receiving this mail because:
You are the QA Contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 26861] parse-xml-fragment-022 should allow error XPST0005

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26861

--- Comment #1 from Michael Kay <[hidden email]> ---
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.

--
You are receiving this mail because:
You are the QA Contact for the bug.