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 #6055 concerns the use of optional features in the "XQuery Update Validation Tests" group. In looking at this bug, I found other test cases in which optional axes have been used: complex-deletes-q1 complex-deletes-q2 complex-deletes-q6 complex-deletes-q7 complex-deletes-q8 complex-deletes-q9 complex-replacevalues-q1 complex-replacevalues-q2 complex-replacevalues-q6 complex-replacevalues-q7 complex-replacevalues-q8 complex-renames-q2 complex-renames-q3 complex-renames-q4 John, please rewrite these tests, avoiding the use of optional axes.
The point of those tests is that they try to examine all aspects of the update (indexes, "redundant" data in the storage format etc.), to ensure a successful update. The axes used are an essential part of the tests. There seems to be precedent for three courses of action: 1) Leave the tests in - implementations that do not support the full axis feature can leave comments in their test results (the way that PSVI support is handled in the XQuery test suite). 2) Move the tests to an optional section of the test suite (the way that full axis tests are handled in the XQuery test suite). 3) Remove the tests altogether.
I'm fine with your second alternative. You might want to move these test cases to a new top-level group called "Additional Tests".
I've moved these tests to a new "FullAxis" test group under the "Optional" test group, which is where full axis tests appear for the XQuery test suite.