Project

Profile

Help

Bug #4972

XQuery Update testing

Added by Michael Kay about 1 month ago. Updated 5 days ago.

Status:
Resolved
Priority:
Low
Category:
Build and release
Sprint/Milestone:
-
Start date:
2021-04-17
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:

Description

It appears that our routine automated testing does not exercise the XQuery Update test suite.

It's especially unclear what the status is of XQuery Update testing on .NET

History

#1 Updated by Michael Kay about 1 month ago

Note also, as far as I can see the W3C test suite for XQuery Update has not been migrated to GitHub.

#2 Updated by Michael Kay 28 days ago

I'm tempted to tackle this by merging the XQuery Update tests into the main QT3/QT4 test suite.

The stylesheet convertFromXQTS.xsl that was originally used to create the QT3 tests from the old XQuery test suite still exists in the tools directory of qt3, and could be adapted to convert the XQUTS tests.

The only new requirement is to express assertions against the result document arising as a result of the update (rather than against the primary query result), and that's not really very different. Test drivers would only need a small amount of change to handle this.

#3 Updated by Michael Kay 28 days ago

I have made good progress in converting the update test suite to standard QT3 format. Main glitches are:

(a) most of the tests rely on XML tree comparison of the result, which is notoriously prone to whitespace problems

(b) there are 39 tests that do multiple phases (i.e. not just a single updating query and then an assertion against the result; multiple phases is going to require explicit support in the QT3 test catalog format and in test drivers.

#4 Updated by Michael Kay 5 days ago

  • Status changed from New to Resolved

I completed the integration of XQuery Update tests into the QT4 test suite. The multi-phase tests are handled by allowing the <test-case> element to contain a sequence of test elements: the second and subsequent queries take the output of the previous query as input. Test drivers have been updated to handle this format.

Please register to edit this issue

Also available in: Atom PDF