Re: [xsl] junit test... for xslt2?

[Dave Pawson <davep@xxxxxxxxxxxxx>]

On 08/03/10 10:43, Andrew Welch wrote:

> >   Here is a simplified exerpt of a test suite for the EXPath HTTP
> > Client:
> >
> >     <t:call function="http:send-request">
> >        <!-- some param here... -->
> >     </t:call>
> >     <t:expect test="count($t:result) eq 2"/>
> >     <t:expect test="$t:result[1] instance of element(http:response)"/>
> >     <t:expect test="$t:result[1]/xs:integer(@status) eq 200"/>
> >     <t:expect test="$t:result[2]/*">
> >        <pass>...</pass>
> >     </t:expect>
>
> Ok this is a good example of the concept behind xchecker... that test
> can easily be rewritten in XSLT - what you gain from the framework you
> also lose in it restrictions (failure messages, variables etc).
> There's nothing wrong with that at all by the way, I just think a
> slightly different (and better) approach is possible.


Is this a case of needing something 'outside' of XSLT?
Perhaps a simple Java framework to allow for testing failures?
Call the transform with 'bad' data to trap all the xsl:message
terminate='yes', then having done that, move in to XSLT
to test for 'good' paths?

Any failures in this second phase are definitely terminal.


regards

--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk