xsl-list
[Top] [All Lists]

Re: [xsl] xslt test automation

2010-11-30 14:55:08

"The requirement is that all output data not normally accessible to
 XSLT-based frameworks is collated into a single XML resource,"

As a requirement of what testing you want to do I find that a bit
on the vague side?

Given a requirement to 'produce a transform to take Schema X instance
and produce something to Schema Y', what requirement would you
put on the testing of the work done by the XSLT author?

Some easy ones, some not so easy. "Has he/she done their job/what was
asked of them" is part of the question to answer.

I'm sure there's lots more than that.

Far easier to test XSLT 2.0 functions against expected values etc.
How much can you mess with the XSLT being tested before someone cries
foul?

If you want to test only parts of the transform, would you need to
include the default templates? Some very grey areas Phil.




--

regards

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

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--

<Prev in Thread] Current Thread [Next in Thread>