29258 2015-11-03 16:38:01 +0000 [QT3TS] omitted Expr in EnclosedExpr 2016-03-09 22:54:17 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Candidate Recommendation All All RESOLVED FIXED P2 normal --- 1 jmdyck oneil christian.gruen josh.spiegel mike public-qt-comments oldest_to_newest 124061 0 jmdyck 2015-11-03 16:38:01 +0000 In the resolution of Bug 29185, XQuery 3.1 has changed {Expr} to {Expr?} at various points in the grammar. So a few tests that were illegal in older versions are legal in XQuery 3.1. Consequently, the following tests should be split into 3.1 and pre-3.1 versions, with different expectations: prod/CompCommentConstructor.xml#K2-ComputeConComment-4 prod/CompTextConstructor.xml#K2-ConText-5 prod/UnorderedExpr.xml#K-OrderExpr-1 prod/UnorderedExpr.xml#K-OrderExpr-2 misc/CombinedErrorCodes.xml#K-CombinedErrorCodes-13 misc/CombinedErrorCodes.xml#K-CombinedErrorCodes-14 misc/CombinedErrorCodes.xml#K-CombinedErrorCodes-15 124123 1 josh.spiegel 2015-11-06 17:52:38 +0000 Also this one: prod/DirElemContent.xml#K2-DirectConElemContent-26 124125 2 jmdyck 2015-11-06 21:57:12 +0000 (In reply to Josh Spiegel from comment #1) > Also this one: > prod/DirElemContent.xml#K2-DirectConElemContent-26 No, K2-DirectConElemContent-26 is only for XQ10 and XQ30. The XQ31+ version is K2-DirectConElemContent-26a 124126 3 josh.spiegel 2015-11-06 22:36:26 +0000 Yes, you are right. I was looking at the github mirror (https://github.com/LeoWoerteler/QT3TS) which appears to have stopped updating back in October. This test was fixed recently. 124336 4 christian.gruen 2015-12-02 10:33:04 +0000 (In reply to Josh Spiegel from comment #3) > Yes, you are right. I was looking at the github mirror > (https://github.com/LeoWoerteler/QT3TS) which appears to have stopped > updating back in October. Thanks for the reminder. Since today, the mirror is updated again. 124347 5 josh.spiegel 2015-12-02 17:24:26 +0000 Thanks! I have found it very useful when searching for tests and looking at change history. 124435 6 oneil 2015-12-15 16:01:02 +0000 I have added new test case which are variants of the ones suggested in comment #0. Committed to cvs 125419 7 mike 2016-03-09 22:54:17 +0000 I have corrected the expected results of prod/CompCommentConstructor.xml#K2-ComputeConComment-4 (It should produce a comment with zero-length content. For some reason text{} produces an empty sequence but comment{} produces a zero-length comment node.)