[Webtest] Anyone producing test documentation with XSLT?

Oster Nathan webtest@lists.canoo.com
Sat, 3 Apr 2004 13:01:28 -0500


This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C4197B.C8130CE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Is anyone currently using XSLT to transform their test cases into HTML
documentation?  
 
I've reviewed the archives and found references to this technique, but
as I'm not experienced with XSLT, I could really use an example.
 
The challenge in my organization is that Test Case documentation is
required, and I don't want to maintain both text-based scripts (in Word
or Excel) AND the Canoo tests.  For the developers/testers, the XML test
cases themselves are all the documentation we need, but I think that
many non-testers on the team would have difficulty reading the XML.  If
"non-technical" folks won't read them, we miss out on the chance to get
valuable feedback on our acceptance tests from customers and management.
 
In the spirit of "test first," I need to show customers a cleanly
formated document for a FAILING test so they can say, "Yes, that has to
pass."
 
Thanks,
Nate

------=_NextPart_000_0001_01C4197B.C8130CE0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial size=3D2>Is =
anyone currently=20
using XSLT to transform their test cases into HTML documentation?&nbsp;=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial size=3D2>I've =
reviewed the=20
archives and found references to this technique, but as I'm not =
experienced with=20
XSLT, I could really use an example.</FONT></SPAN></DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial size=3D2>The =
challenge in my=20
organization is that Test Case documentation is required, and I don't =
want to=20
maintain both text-based scripts (in Word or Excel) AND the Canoo =
tests.&nbsp;=20
For the developers/testers, the XML test cases themselves are all the=20
documentation we need, but I think that many non-testers on the team =
would have=20
difficulty reading the XML.&nbsp; If&nbsp;"non-technical" folks won't =
read=20
them,&nbsp;we miss out on the chance to get valuable feedback on our =
acceptance=20
tests from customers and management.</FONT></SPAN></DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial size=3D2>In the =
spirit of=20
"test first," I need to show customers a cleanly formated document for a =
FAILING=20
test so they can say, "Yes, that has to pass."</FONT></SPAN></DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial=20
size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D579575017-03042004><FONT face=3DArial=20
size=3D2>Nate</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_0001_01C4197B.C8130CE0--