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 9531 - 3 query names are (partially) misspelled in the catalog
Summary: 3 query names are (partially) misspelled in the catalog
Status: CLOSED FIXED
Alias: None
Product: XQuery Update Facility Test Suite
Classification: Unclassified
Component: XQuery Update Facility Test Suite (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-15 18:56 UTC by Nikolay Ognyanov
Modified: 2010-04-21 17:09 UTC (History)
0 users

See Also:


Attachments

Description Nikolay Ognyanov 2010-04-15 18:56:24 UTC
For 3 queries testcase/state/query/@name is different from testcase/@name. Please find bellow cvs diff between my fixed catalog and catalog in the CVS.

cvs diff -u XQUTSCatalog.xml 

Index: XQUTSCatalog.xml
===================================================================
RCS file: /sources/public/2007/xquery-update-10-test-suite/XQUTSCatalog.xml,v
retrieving revision 1.74
diff -u -r1.74 XQUTSCatalog.xml
--- XQUTSCatalog.xml	13 Apr 2010 01:16:30 -0000	1.74
+++ XQUTSCatalog.xml	15 Apr 2010 18:38:28 -0000
@@ -10848,7 +10848,7 @@
                   section-title="Revalidation Declaration"
                   section-pointer="id-revalidation-declaration"/>
                <state time="0">
-                  <query name="revalidation-declaration-01" date="2008-10-16"/>
+                  <query name="revalidation-declaration-01-fail" date="2008-10-16"/>
                   <input-file role="principal-data" variable="input-context">emptydoc</input-file>
                   <expected-error>XUST0026</expected-error>
                </state>
@@ -11138,7 +11138,7 @@
                   section-title="Revalidation Declaration"
                   section-pointer="id-revalidation-declaration"/>
                <state time="0">
-                  <query name="revalidation-declaration-03" date="2008-10-16"/>
+                  <query name="revalidation-declaration-03-fail" date="2008-10-16"/>
                   <input-file role="principal-data" variable="input-context">emptydoc</input-file>
                   <expected-error>XUST0026</expected-error>
                </state>
@@ -11729,7 +11729,7 @@
                   section-title="Revalidation Declaration"
                   section-pointer="id-revalidation-declaration"/>
                <state time="0">
-                  <query name="revalidation-declaration-05" date="2008-10-16"/>
+                  <query name="revalidation-declaration-05-fail" date="2008-10-16"/>
                   <input-file role="principal-data" variable="input-context">emptydoc</input-file>
                   <expected-error>XUST0026</expected-error>
                </state>
Comment 1 Andrew Eisenberg 2010-04-15 19:30:06 UTC
Hmmm. I count 76 test cases where (test-case/state/query)[1]/@name is different from test-case/@name.

The two names are used for different purposes. test-case/@name is used to identify the test case for the purpose of submitting results and generating reports. (test-case/state/query)[1]/@name is used to identify the query or XQueryX that is being executed as part of a test case. The two are often the same, but they need not be.

XQUTS 1.0.0 was published some time ago and we hope very shortly to publish XQUTS 1.0.1. We are making only substantive changes at this time, and so I'd like to make no change to these names.

Please close this bug report if you are satisfied with this resolution.
Comment 2 Nikolay Ognyanov 2010-04-15 20:58:59 UTC
Thank you for the clarification. Sorry for the distraction.
Comment 3 Nikolay Ognyanov 2010-04-15 22:10:56 UTC
P.S.: After some more digging - my real problem with these test cases is that their scenario is "parse-error" but the way their names are defined in state/query/@name they actually point to queries which pass syntax check. For example revalidation-declaration-01 is the name of query in the sole state of test case revalidation-declaration-01-fail which has scenario "parse-error". The query revalidation-declaration-01 though passes syntax check and is also present in the sole state of test case revalidation-declaration-01 with status "standard". At the same time query revalidation-declaration-01-fail does exist and raises syntax error. So apparently state/query/@name for test case revalidation-declaration-01-fail should be revalidation-declaration-01-fail. Situation with the other 2 test cases is the same.

With 1.0.1 pending shortly it is up to you to decide whether the problem substantive enough for a fix this in 1.0.0, so I am not reopening the bug.
Comment 4 Andrew Eisenberg 2010-04-19 18:42:56 UTC
I agree that these test cases should use scenario "standard" rather than "parse-error" and have made these changes to our catalog. The test cases that I have changed are:

revalidation-declaration-01-fail
revalidation-declaration-03-fail
revalidation-declaration-05-fail
Comment 5 Nikolay Ognyanov 2010-04-21 17:09:46 UTC
Thank you.