- From: <bugzilla@jessica.w3.org>
- Date: Mon, 08 Sep 2014 09:42:23 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26753 johnlumley <john@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|abel.online@xs4all.nl |john@saxonica.com Severity|normal |minor --- Comment #1 from johnlumley <john@saxonica.com> --- current-output-uri-00[23] assert ends-with(/out,'fn/current-output-uri/results...') to check the determined output-uri for a normal and a result document. These locations are relative to the test sources, but the XTtest schema suggests that this might not be the correct location. The documentation for assert-result-document/@uri states: The uri corresponds to the URI used in the href [error in schema documentation - should be uri - jwL] attribute of the xsl:result-document instruction. It is supplied as a relative URI, interpreted as being relative to the implicit base output URI chosen by the test driver. Hence it is possible (or even likely) that the outputs (and hence values) could be elsewhere. A common alternative case might be where all results are held in a single separate file tree, such that: current-output-uri-102: <assert>ends-with(/out,'current-output-uri-002.xml') current-output-uri-103: <assert-result-document uri="second/current-output-uri-003.xml"> <assert>ends-with(/out,'second/current-output-uri-002.xml') These tests can be added as alternatives, but aren't particularly taxing. I'll think about some more taxing possibilities. [Sorry about the title spelling - finger trouble and hitting Ctrl-S too early] -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 8 September 2014 09:42:25 UTC