Inline script

[bertfrees]

Support defining an XProc script inline in the XProcSpec test. (This is just an idea, I have no actual use case for it yet, but it seems useful.)

[rom1mouret]

I do call some XProc filters to post-process the result in order to make the <p:except type="compare"> simpler to use, especially when some ids have been randomly generated by the script to test. Inline XProc would be useful for this indeed. In the meantime, the <x:call script="..."> can call an XProc step wrapper that includes the filter.

[josteinaj]

There should be support for defining your own type of assertions. Check out
this for an example of an assertion that tests for an xml declaration:

https://github.com/josteinaj/nordic-epub3-dtbook-migrator/blob/master/nordic-epub3-dtbook-migrator/src/test/xprocspec/epub3-to-dtbook.xprocspec
https://github.com/josteinaj/nordic-epub3-dtbook-migrator/blob/master/nordic-epub3-dtbook-migrator/src/test/xprocspec/xprocspec-assert-xml-declaration.xpl

As for unpredictable values, you can test portions of the result but that's
not always a solution. XSpec let's you put three dots ("...") in attribute
values and text nodes to represent "any content here". Would that be a good
solution?

Would you like some filtering functionality added to the context element as
well?
13. feb. 2014 18:48 skrev "Romain Mouret" [email protected]
følgende:

I do call some XProc filters to post-process the result in order to make
the simpler to use, especially when some ids have been randomly generated
by the script to test. Inline XProc would be useful for this indeed. In the
meantime, the can call an XProc step wrapper that includes the filter.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-35005198
.

[bertfrees]

We're a bit wandering of track now, but anyway, here is another example were custom assertions are used:

https://github.com/daisy-consortium/pipeline-mod-braille/blob/master/pipeline-braille-utils/liblouis/liblouis-formatter/src/test/xprocspec/test_format.xprocspec
https://github.com/daisy-consortium/pipeline-mod-braille/blob/master/pipeline-braille-utils/liblouis/liblouis-formatter/src/test/xprocspec/pef-compare.xpl

This works great for me. The three dots would be a nice additional feature, although I don't think I would use it. I also have to deal with randomly generated identifiers, but that was not the only reason for creating a special pef:compare step.

[josteinaj]

allow

<x:script>
    <p:declare-step/>
</x:script>

as the first child of x:description as an alternative to the x:description/@script attribute.