Hi Florent,
thanks for your input.
I am playing around with basex-tests [1]. I cloned the repository, then went to the directory and tried "mvn test". I got a compilation error:
The error seems to point to an automatically generated class, which contains a string with (way) too many characters. Good to know that everything works with "mvn compile", so I'll currently leave it like that for now..
I have two remarks. 1/ The second test case fails because BaseX tries to resolve sample.xml in the current directory, but it should be resolved relatively to the catalog file.
Out of interest: could you try switch to your test directory and run the tests from there? This is probably what most of us do. To be honest, I'm not even sure if someone in the team uses the -p flag at all, although I mentioned it to you in one of my last e-mails.
2/ BaseX creates a file "qt3ts.log" in the test suite directory. I couldn't find any infos in the FOTS doc about where to put the result, but Saxon does that in results/saxon/, which is probably better in order to avoid interferences between several processors.
Yes, this could be done.. But hasn't been considered so far, as we only use the code to test our own implementation. As the QT3TS code is coupled pretty tightly to our implementation, we'll probably stick with the status quo (unless the code will be adapted by someone to also work for other Java implementations). I guess that Leo's XQuery FOTS code (or a slightly enhanced version of it) could be adapted much easier to other implementations, as most of the code is written in pure XQuery 3.0 [1].
Hope this helps, Christian