- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Nov 2014 19:01:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27371
Bug ID: 27371
Summary: Tests like Serialization-009 should allow the error to
be raised during evaluation
Product: XPath / XQuery / XSLT
Version: Working drafts
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: XQuery 3 & XPath 3 Test Suite
Assignee: oneil@saxonica.com
Reporter: josh.spiegel@oracle.com
QA Contact: public-qt-comments@w3.org
<test-case name="Serialization-009"
xmlns="http://www.w3.org/2010/09/qt-fots-catalog">
<description>
It is a serialization error [err:SEPM0016] if a parameter value is
invalid for the given parameter.
Wrong serialization parameter value for doctype-public.
</description>
<created by="Dennis Knochenwefel" on="2011-12-05"/>
<dependency type="spec" value="XQ30+"/>
<test><![CDATA[declare namespace output =
"http://www.w3.org/2010/xslt-xquery-serialization";
declare option output:doctype-public "쎁";
<result>ok</result>
]]></test>
<result>
<any-of>
<!-- the processor may use these parameters to control the way in
which the serialization takes place.
It is the responsibility of the host language to specify how
invalid values should be handled at the level of that language. -->
<assert-xml><![CDATA[<result>ok</result>]]></assert-xml>
<!-- It is a serialization error [err:SEPM0016] if a parameter value
is invalid for the given parameter. -->
<assert-serialization-error code="SEPM0016"/>
</any-of>
</result>
</test-case>
This test uses assert-serialization-error to test for SEPM0016. Here is the
definition of assert-serialization-error:
"Asserts that the query can be executed without error, but serializing the
result
produces a serialization error.
The result of the query must be serialized using the serialization
options specified within the query (if any)."
I think in this case, the test should also allow the error to be thrown during
expression processing. From XQuery 3.0, 2.4.4:
"A processor that is not performing serialization may report errors if any
serialization parameters are incorrect, or may ignore such parameters."
So I would like to add an alternate result:
<error code="SEPM0016"/>
And I would like to make the same type of fix to the following tests as well:
Serialization-010
Serialization-011
Serialization-012
Serialization-015
Serialization-017
Serialization-018
Serialization-019
Serialization-020
Serialization-024
Serialization-025
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 19 November 2014 19:01:09 UTC