-
-
Notifications
You must be signed in to change notification settings - Fork 10
Switch tests to xqsuite #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The name for each test was derived from the "title" elements in the original test-plan.xml document. Unfortunately, the fuller descriptions in the "description" element had no counterpart in the xqsuite annotations. The only resource needed from the old resources location was keystore.ks.
|
@joewiz Looks good. Do you mind if I push some commits to this PR to add the parts needed to have it run via XQSuite in Maven etc? |
|
@adamretter Not at all! Please push and modify as you see fit. Thank you! |
|
@adamretter Doh! I should've given the test module the |
|
Tests will now run with |
and fix lines with only one space
|
@adamretter Cool! The xqsuite has one remaining problem on line 52, where I had to hardcode a reference to the directory containing the I'm not actually certain that the xqsuite needs this resource. The original tests used keystore.ks in the tests for crypto:generate-signature and crypto:validate-signature, but it doesn't appear to actually use them. Can we really jettison this resource and expect the tests of these functions to perform correctly? @nsincaglia Do you use the |
… to provide extra context about the tests
|
Interestingly, the tests in baseX generate the necessary signatures. I do like that approach a lot. |
…ions and variables
I have fixed this now, it just needs to be in the correct Java classpath, then you can use |
|
@adamretter thanks a lot, looks good to me. |
This PR adapts the original java-based tests to use xqsuite and deletes the java tests, with the aim of running the tests via Maven and in CI.