> Leaving aside the two questions of whether or not schema awareness is
> always an option (e.g., when you are using translets) and of exactly how
> much automated checking is "fashionable" for XSLT to begin with, neither
> schema awareness nor unit testing is a panacea.

I guess I should explain that bit...

- agile development is fashionable, and one of its essentials is
automated testing, typically unit tests

- xml schema is not fashionable, and schema-awareness will never get a
mention because all of the agile related material out there is for
other languages.  Those people teaching agile will always use unit
tests as the way to reduce errors.  None of the agile evangelists will
know about result validation, so it won't get a mention as a suitable
technique, even though for XSLT its arguably the first thing to do.


> I'm all for testing it in as many ways as possible for the least effort
> and the maximum confidence in the result.  So using schema awareness
> when it is an option is perfectly fine by me.

yep, it's all good, by the way the link gives me an error - the
security certificate is not valid

> [1] https://www.menteithconsulting.com/wiki/XTech2007/MyStylesheetRunsBut#EffectivenessofUnitTesting



-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/