This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24053 - [XT3TS] Test cases with tilde in patterns
Summary: [XT3TS] Test cases with tilde in patterns
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Abel Braaksma
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2013-12-10 16:00 UTC by Vitaliy
Modified: 2015-05-06 21:15 UTC (History)
3 users (show)

See Also:


Description Vitaliy 2013-12-10 16:00:24 UTC
There are several test cases: from match-127 to match-135, which uses old Tilda syntax. 
At the same time test-set folder contains files with fixed syntax: from match-127n.xsl to match-135n.xsl.

Should test cases be updated to use these new fixed stylesheets instead of old ones?
Comment 1 Vitaliy 2013-12-10 16:06:31 UTC
The new tests to replace Tilda syntax already exist. 
I'll rephrase my question - should old Tilda syntax tests be removed?
Comment 2 Michael Kay 2013-12-10 17:09:03 UTC
Yes, the inclusion of both forms is transitional, I felt it inappropriate to delete the old ones until the new WD is out.
Comment 3 Liam R E Quin 2013-12-10 20:12:39 UTC
Possibly better to keep the test cases but to mark them as being expected to fail with syntax errors...
Comment 4 Abel Braaksma 2013-12-13 00:36:40 UTC
I tend to agree with Liam here. Since the tilde-syntax was around for quite a while, it is not unthinkable that processors implemented support for it, while the syntax should now raise an error.

However, we don't need too many of them, I think. Just a couple and change the expected outcome to be a syntax error.
Comment 5 Abel Braaksma 2014-10-30 12:56:34 UTC
Meanwhile, this has been resolved with previous fixes in the XT3 testsets. There are now no tilde-syntax patterns anymore, so I think it would still be a good idea to follow Liam's advice and add a few tests to check that the appropriate static syntax error is thrown.

However, I'll move forward and close this issue as it's original description is resolved.
Comment 6 Abel Braaksma 2015-05-06 21:15:37 UTC
Was resolved > 30 days ago, closing.