26755 2014-09-08 09:53:07 +0000 [XT30TS] current-output-uri-00[23] 2015-04-16 23:51:43 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Test Suite Working drafts PC Windows NT RESOLVED FIXED P2 minor --- 1 john abel.braaksma abel.braaksma john public-qt-comments oldest_to_newest 111165 0 john 2014-09-08 09:53:07 +0000 Tests 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,'results/current-output-uri-002.xml') current-output-uri-103: <assert-result-document uri="results/second/current-output-uri-003.xml"> <assert>ends-with(/out,'results/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. 111166 1 john 2014-09-08 09:53:44 +0000 I'll work through some possible alternatives 111169 2 abel.braaksma 2014-09-08 13:07:12 +0000 *** Bug 26753 has been marked as a duplicate of this bug. *** 119268 3 abel.braaksma 2015-04-07 02:02:22 +0000 It looks like at Sept 11, 2014, these tests were changed to support multiple output locations and where merged six days later, where you seem to have settled for asserting for the locations ending with "results/<expected-filename>" format. This seems to work well, at least in our case. I think we can close this bug, would you agree? 119603 4 abel.braaksma 2015-04-16 23:51:24 +0000 Resolving this bug as fixed, changes have been applied as described in comment#3.