- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Apr 2015 17:07:35 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28581 Abel Braaksma <abel.braaksma@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abel.braaksma@xs4all.nl --- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Yes, the literal result will have extra whitespace for these tests. Please note that these tests use assert-string-value assertions and that the documentation of that assertion says: Asserts that the result of the test, after conversion to a string by applying the expression string-join(for $r in $result return string($r), " ") is equal to the string value of the assert-string-value element. Note that this test cannot be used if the result includes items that do not have a string value (elements with element-only content; function items). If the normalize-space attribute is present with the value true (which is the default), then both the string value of the query result and the value of the assert-string-value element should be processed as if by the XPath normalize-space() function before the comparison. Otherwise, normalization does not take place. This is different from the QT3 test-suite, where the default is "no". The reasoning behind this is that in most tests, esp. with XSLT, extra whitespace can be added to result tree, as in these examples and ignoring the extra whitespace makes for easier tests. Oonly in some situations, not whitespace-normalizing makes sense and then you can either set this explicitly, or you can use assert-xml, assert-eq or other assertions. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 29 April 2015 17:07:36 UTC