22736 2013-07-19 12:56:59 +0000 [XQ3TS] typeswitch-in-xpath 2013-07-19 13:59:46 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Candidate Recommendation PC Windows NT CLOSED FIXED P2 normal --- 1 tim oneil public-qt-comments oldest_to_newest 90982 0 tim 2013-07-19 12:56:59 +0000 The test "typeswitch-in-xpath" appears in a test-set with dependency XQ10+, but the test itself can only be run in XP20+. It's impossible to meet both these requirements simultaneously, and so I think the test can never be run. 90983 1 oneil 2013-07-19 13:04:17 +0000 This test looks OK as it has the XP20+ dependency at the test case level. 90985 2 tim 2013-07-19 13:14:01 +0000 I'm afraid I don't agree. We first test the condition at the test-set level, then the condition in the test-case. The condition at the test-set level should always be as permissive as that in the test-case. Since this is the ONLY case in which this occurs, I believe it to be a bug. As soon as this is fixed, I'll be ready to submit results. 90986 3 mike 2013-07-19 13:17:41 +0000 I think there may be some cases where the author of a test has assumed that a dependency at test-case level masks or overrides a dependency of the same type at test-set level. The way the documentation is written, this isn't the case: the dependencies should be cumulative. So I think Tim is right, if XQ10 is required at test-set level and XQ20 is required at test-case level, then the dependencies for this test case can never be satisfied. 90987 4 tim 2013-07-19 13:20:35 +0000 A quick fix would be to move this test out of prod/TypeswitchExpr.xml and into misc/CombinedErrorCodes.xml. 90988 5 oneil 2013-07-19 13:21:39 +0000 Ok. I will move the test. 90989 6 oneil 2013-07-19 13:26:45 +0000 Bug fixed and committed to cvs. 90990 7 tim 2013-07-19 13:47:15 +0000 Thanks. 90991 8 tim 2013-07-19 13:59:46 +0000 BTW, I've just removed the original version from TypeswitchExpr.xml.