[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Re: xsl/xslt coding standard

Subject: RE: Re: xsl/xslt coding standard
From: "Robert Koberg" <rob@xxxxxxxxxx>
Date: Fri, 16 Aug 2002 09:55:48 -0700
RE:  Re: xsl/xslt coding standard
Hi,

I don't know if this is applicable across a broad spectrum, but in our case
it works well for documentation and testing the XSL(t). This is useful for
people managing multiple projects with a base/starter set of XSL.

Our base set of XSL is copied to the client's project directory. They (or
we) can go about modifying it for specific needs. We are also adding
features to the base set and want to be able to update the client project.
We need to ensure that the base set of xsl:includes, xsl:variables,
xsl:templates, html, et cetera are included in their branch.

I have a {$xsl_filename}_test.xsl (applied against it's namesake) that does
boolean checks to see if each of the base set of elements are present or
not. This creates an XML file that has the test result information and
documentation (which is kept in the test XSL). From this we can create a
documentation HTML that describes the current state of the XSL.

I would be very interested to hear how people do functional or unit testing
with XSL.

best,
-Rob



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.