-
Notifications
You must be signed in to change notification settings - Fork 31
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
Test for base URI #347
Test for base URI #347
Conversation
…a-aware_ant # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…ne-coverage # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…overage # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…-215 # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…talog # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…talog # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…xpected-uri # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…ntext # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
# Conflicts: # test/xspec-bat.cmd # test/xspec.bats
# Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…177_cumulative # Conflicts: # .travis.yml # appveyor.yml # test/xspec-bat.cmd # test/xspec.bats
…c-rule # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…211_cumulative # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…ntext # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…eport # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…l-uri # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…185_cumulative # Conflicts: # test/xspec-bat.cmd # test/xspec.bats
…-tests # Conflicts: # .travis.yml # appveyor.yml # test/xspec-bat.cmd # test/xspec.bats
…overage # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…ne-coverage # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…-bats # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
# Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…xpected-uri # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…talog # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…talog # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…-215 # Conflicts: # .travis.yml # appveyor.yml # bin/xspec.bat # test/xspec-bat.cmd # test/xspec.bats
…177_cumulative # Conflicts: # test/end-to-end/cases/expected/stylesheet/xspec-rule-result.html # test/end-to-end/cases/expected/xspec-rule-junit-norm.xml # test/end-to-end/cases/expected/xspec-three-dots-junit-norm.xml # test/generate-tests-utils.xspec # test/win-bats/collection.xml # test/xspec.bats
# Conflicts: # test/end-to-end/cases/expected/stylesheet/xspec-rule-result.html # test/end-to-end/cases/expected/xspec-rule-junit-norm.xml # test/end-to-end/cases/expected/xspec-three-dots-junit-norm.xml # test/generate-tests-utils.xspec # test/win-bats/collection.xml # test/xspec.bats
…177_cumulative # Conflicts: # test/end-to-end/cases/expected/schematron/schematron-01-result.xml # test/end-to-end/cases/expected/stylesheet/xspec-153-result.xml # test/end-to-end/cases/expected/stylesheet/xspec-ambiguous-expect-result.xml # test/end-to-end/cases/expected/stylesheet/xspec-focus-1-result.xml # test/end-to-end/cases/expected/stylesheet/xspec-function-result.xml # test/end-to-end/cases/expected/stylesheet/xspec-import-result.xml # test/end-to-end/cases/expected/stylesheet/xspec-pending-result.xml # test/end-to-end/cases/expected/stylesheet/xspec-xslt2-result.xml
@galtm Also, I think |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great.
Sure. I was thinking of adding one scenario for /x:description/x:variable and one for //x:scenario/x:variable. Is it worthwhile for me to check the case where the variable definition uses |
Thanks, @galtm.
I'm not quite sure... So please add any test cases as you find useful and let's see what happens. @cirulls |
This pull request derives from #345. So needs to be handled after that.
This pull request just adds some tests to ensure that the external files such as
x:import/@href
are loaded via the base URI.xml-base.xspec
is both for XQuery and XSLTxml-base_stylesheet.xspec
is only for XSLT