Skip to content
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

How to handle broken/invalid test cases? #16

Closed
line-o opened this issue Nov 19, 2020 · 2 comments
Closed

How to handle broken/invalid test cases? #16

line-o opened this issue Nov 19, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@line-o
Copy link
Member

line-o commented Nov 19, 2020

Inspecting the test results I found at least six test cases using the old map constructor syntax :=.
These tests fail now due to an error code mismatch (query throws with XPST0003 instead of FOJS0001)

How can we maintain an updated test suite?

  • fn-parse-json-924
  • fn-parse-json-925
  • fn-parse-json-926
  • fn-parse-json-927
  • fn-parse-json-928
  • fn-parse-json-929
@line-o line-o added the enhancement New feature or request label Nov 19, 2020
@line-o
Copy link
Member Author

line-o commented Nov 19, 2020

from #14 : use target/scala-2.13/exist-xqts-runner-assembly-1.0.0.jar -x HEAD to get the current, maintained testsuite

@line-o line-o closed this as completed Nov 19, 2020
@adamretter
Copy link
Contributor

@line-o running exist-xqts-runner-assembly-1.0.0.jar --help will show you all of the options :-p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants