W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2016

[Bug 29717] New: [xslt30ts]There are no tests testing the functionality of xsl:merge for-each-item other than merge-042 which only checks an error condition

From: <bugzilla@jessica.w3.org>
Date: Wed, 06 Jul 2016 12:03:54 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29717-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29717

            Bug ID: 29717
           Summary: [xslt30ts]There are no tests testing the functionality
                    of xsl:merge for-each-item other than merge-042 which
                    only checks an error condition
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0 Test Suite
          Assignee: abel.online@xs4all.nl
          Reporter: martin.honnen@gmx.de
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

The current specification does not contain a single example using xsl:merge
for-each-item and when searching through the test suite I have not found a
single test case demonstrating and checking the functionality of xsl:merge
for-each-item, other than merge-042 checking the error XTSE0020 that both
for-each-item and for-each-stream are used at the same time.

Shouldn't there be test cases using xsl:merge for-each-item?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 6 July 2016 12:04:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:01 UTC