Re: [xsl] XSLT Unit Testing and Coverage

["alex.g.muir@xxxxxxxxx alex.g.muir@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

I find that visualizing effectively what is occuring to input as it moves
through to output is the most crucial thing needed to get to a correct
solution quickly. Often that means i convert xml output into colour coded html
output.  i create input files that test all the functionality based on
analysis of the input and put those into a harness to confirm equality of
current output with previous output which may often differ as development
progresses so the visual representation becomes key in the process to confirm
things work. .

Alex

-----Original message-----
From: Vasudev Kandhadai vasu.kandhadai@xxxxxxxxx
Sent:  05/28/2014, 6:57  PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] XSLT Unit Testing and Coverage


Dear All,
is there a good reason to deploy a XSLT unit testing framework? I have
never seen any serious XSLT dev env where the XSLT unit testing was either
done religiously, or considered mandatory.  Other than a very religious
Java development team with strict Junit set up with Maven etc, who have
adopted XSLT into their dev env, who would now want to extend the same
ideologies to the XSLT world?  I have personally never used or utilized
practically any XSLT unit testing framework in any project and nor was
there any requirement to do so...

So considering we need to do this, I came across,
XSPEC, XUnit etc.. Xspec seems like a good one,  but doesnt look like a lot
of discussions are  happening in the community.. The Coverage feature
doesnt work ...
The class is not being maintained.

Cakupan, was very hard on my brains to read the manual.. Again something
that has been out there for a while and not sure it is still maintained /
supported.

Does anyone has any ideas on what options we have in the XML world for
XSL Unit Testing + Coverage Report

I tried posting to the Xspec community but no one bothered to answer my
questions , so I am inclined to think it is dead.

Somehow I am also inclined to think Coverage feature is a very
Java/C#/C/C++ paradigm... Doesnt make too much sense with the XSLT world?

Your inputs are valuable.
Kandha.