xprocspec v1.4.2

• Support loading input documents from ZIP (previously only supported within context and expect)
• Make compatible with "general-values"-enabled XMLCalabash

xprocspec v1.4.1

• Fix bug in handling of namespaced parameters (#77)

xprocspec v1.4.0

For more information on how to use xprocspec, visit the xprocspec homepage.

Changes

• #71: Print message with label of currently running scenario
• #75: Better implementation for loading files from a ZIP
• #74: Fix Travis URL

xprocspec v1.3.1

For more information on how to use xprocspec, visit the xprocspec homepage.

Minor changes

• Change surefire report so that we can generate better textual output
• Travis: enable super/* branches
• Test with Calabash 1.1.20
• xml:base attributes in xprocspec tests were causing errors

xprocspec v1.3.0

For more information on how to use xprocspec, visit the xprocspec homepage.

New features

• Support "ordered" argument on x:document type='zip' (issue #61)
• Add x:document type='zip' to the schema
• Added progress indication attributes for use by DAISY Pipeline 2

xprocspec v1.2.0

For more information on how to use xprocspec, visit the xprocspec homepage.

New features

• Make it easier to assert for specific error codes and messages (issue #21)
• xprocspecs message step definition is now aligned with the message step in DAISY Pipeline 2 (issue #23)
• A script is no longer required if there is a x:import element present (issue #27)
• Support refencing files inside ZIP files (issue #32)
• White space differences in text and attributes are now highlighted in report (issue #33)
• Let xfail attribute have a comment as a value (issue #34)
• Make xfail attribute work on x:scenario elements (issue #40)
• Improve performance (issue #41)
• Allow a sequence of xprocspec documents as input (issue #42)
• Allow focus attribute on x:description element (issue #45)

Bugfixes

• Specifying primary parameter port generated duplicate ports (issue #9)
• Ports with no results gave a 'port not found' warning (issue #31)
• If a file (or directory) referenced by x:document does not exist; there should now be an error message (issue #35)
• The port attribute on x:param is now added to the documentation and the schema (issue #36)
• Error when there's a comment in x:context (issue #38 and issue #43)

See also

• Closed issues
• xproc-maven-plugin v1.0.0

xprocspec v1.1.0

For more information on how to use xprocspec, visit the xprocspec homepage.

New features

• side-by-side XML diff (issue #12)
• Show detailed diff for failing type="compare" assertions (issue #19)
• New x:documentation element for documenting tests (issue #18)
• added support for inline scripts. The x:script element can now be used as an alternative to the script attribute. (issue #17)
• xfail attribute on x:expect - inverts the results of assertions (issue #16)

Bugfixes

• Total test count reported wrongly when target script does not exist (issue #20)
• problem using 'temp-dir' as option name (issue #4)
  * select attribute on x:document not working properly
• an error is now thrown (XSP03) when you refer to a non-existing port using x:document
• fixed issue with x:import not working when tests are stored in different directories
• allow p:library imports (issue #5) and fix non-existing directories (issue #13)
• fix for temp-dir files getting wrong base-uri
• more human-readable error messages (issue #11)

See also

• Closed issues
• xproc-maven-plugin v1.0.0

xprocspec v0.2-alpha

Changes include

• added support for pending tests
• improved the reports; the HTML-report now looks like the XSpec reports
• added test suite for testing the features of xprocspec
• a lot of bugfixes

xprocspec

xprocspec is a tool for testing XProc scripts. It is based purely on XProc, but depends on Calabash for dynamic evaluation of pipelines.

The project homepage can be found here: http://josteinaj.github.io/xprocspec/

Some features:

• Test grammar based on the XSLT-testing tool XSpec, but somewhat modified to better suit XProc
• Use ports, errors, directory structures or files as test contexts
• Make assertions against the test contexts in terms of XPath expressions or document comparisons

For anyone who wants to try it out; expect bugs. Check out the GitHub repository and have a look at the bundled example.

Feedback appreciated!