Allow context in named templates #76
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PR-76 issue #66 allow context in named templates
|
Looks good to me, thank you! Any objection on this one? @tgraham-antenna ? |
|
Are there any updates on this issue? @tgraham-antenna |
added 25 commits
August 10, 2016 08:27
- fix code coverage in shell script - update Java class XSLTCoverageTraceListener for SaxonEE/PE 9.7 - unit tests for shell script
# The first commit's message is: #2 initial commit # This is the 2nd commit message: add saxon9he # This is the 3rd commit message: remove cat and saxon # This is the 4th commit message: add tests
- replace saxon:serialize() with fn:serialize and use XSLT 3.0 - output error message for Saxon8 and Saxon8-SA - update XSpec unit test (unit test requires support for XSLT 3.0 to run as requested in #74) - update bats unit test
- remove TRAVIS_BUILD_DIR variable and use current working directory (pwd)
….xspec (only for XSLT) (#83) * migrate shared XSLT and XQuery tests from generate-tests-utils.xspec to generate-x-utils.xspec * add TODO comments in generate-tests-utils.xspec for incomplete XQuery tests
- fixes #62 - Remove tests for report-atomic-value() - Migrate tests for node-deep-equal() to generate-tests-utils.xspec - Remove tests for test:deep-equal() - Migrate tests for item-deep-equal() to generate-x-utils.xspec - Migrate tests for sorted-children() to generate-tests-utils.xspec - Migrate tests for report-value to generate-tests-utils.xspec
- fixes 95
* exclude xmlns:x and xmlns:pkg * fixes 90
* fixes #119 * escape apostrophe in URI to run XSpec test with folder containing an apostrophe in its name * add tests for shell and batch scripts
* closes #121 and #122 * add additional checks for using the Saxon script with EXPath Packaging system * add a test for the shell script
* closes #75
* closes #128
* add XProc harness for BaseX standalone (review #103) - add XProc harness for BaseX 8.6.4 standalone - add Travis configuration for BaseX - add test for BaseX - add tutorial files for XQuery * create directory for BaseX * add double square bracket in condition * add semi-colon * add semi-colon in condition for test * test whole output message instead of line
… up temporary files (#131) Suppress warning message in Schematron compilation and clean up temporary files
Allow Schematron XSLTs to be provided externally
* Added new element x:expect-rule to test that a Schematron rule is fired/thrown. * Added new attribute @count to test that an Schematron assert, report, or rule is thrown a specific number of times. * Changed the RelaxNG grammar to allow x:expect in scenarios that have Schematron-specific expect elements. * Changed the location of the compiled Schematron XSLT to the same folder as the Schematron so that relative file paths that are used within the Schematron will work. * Extended the @id attribute matching to include the @id attribute on the Schematron pattern element. * Allow the @Label attribute on Schematron-specific expect elements. * Added more unit tests for Schematron support including: relative file path to locate a dependency; embedded XSLT function; id attribute on assertion, rule, pattern and imported; abstract pattern; abstract rule; x:expect-rule; @count
* Modified the HTML report to include CSS inline and include the success/fail/pending images from oXygen inline as one file. * Right align edges in the HTML report * Reduce left and right body margins in the HTML report * Remove auto-capitalization of scenario labels * Added parameter "inline-css" to format-xspec-report.xsl. If set to value other than "false" will cause the report CSS to be included in the HTML report file instead of referenced. Default is false (safe for XProc). xspec.bat and xspec.sh set the parameter to true, * Report formatting changes including to display passed / pending / failed / total counts similar to oXygen report format.
* Add tests for shell and batch scripts for #135
- add steps to run XSpec test for Schematron in Ant build script - add basic documentation to run Ant build script via command line and oXygen - install Ant 1.9.8 in Travis and AppVeyor configurations - standardize and refactor Travis and AppVeyor configuration - add tests for running XSpec test for Schematron with Ant build script - add tests for running XSpec test for XSLT with Ant build script - add JavaScript function to get file path from URL (used in Ant build script) - use resolve-uri function in XSLT transformation for Schematron
* Add attribute xspec and attribute schematron to XML report * Add attribute xspec-original-location to intermediate XSpec file for Schematron * Add testsuites/@name to JUnit XML * Improve the HTML report header title for Schematron tests * Add end-to-end tests for XQuery and Schematron
Also * Enhance it to be able to inline css * Update xspec.sh and xpsec.bat to enable inline css (aligned with #135)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue #66
XSpec schema updated to allow context element in named-scenario (just as it is already allowed in matching-scenario)
generate-xspec-tests.xsl had code to deal with context in this position, but written with incorrect $context - now changed to $impl:context