How should we approach adding tests to mvn to ensure our build is not
breaking XQuery functionality? The tests must pass to be added to the build
process. The current build tests include parallel tests that are not
covered in the XML Query Test Suite (XQTS). The XQTS has 20,000 tests that
cover XQuery specification although currently only about half of the tests
pass in VXQuery. In addition, running all those tests takes a few minutes.

How can we ensure quality maven builds during development with the
inclusion of more XQuery testing? Off the top of my head, we have two
options:
 1. We could pick and choose small test groups from of the XQTS test suite
to run.
    + Test have already been written.
    - XQTS must be downloaded.
    - Tests may not line up with build test goals.
 2. Write our own small test list for basic XQuery functionality.
    + Tests will be created specifically for VXQuery.
    - Must create all tests.

In both cases, the full XQTS test suite would be used for a more thorough
and complete testing.

What do you think?

Reply via email to