Re: [Perlunit-users] Fw: Re: Generate HTML reports from unit test results
Status: Beta
Brought to you by:
mca1001
From: Roger D. <rog...@gl...> - 2006-05-09 12:36:51
|
As a lightweight alternative - and the easiest way forward - you can assoiciate a Cascading Style Sheet with an XML document and achieve the same result in most modern browsers. OTOH, using the Perl Document Object Model API for XML documents will give you a tool which doesn't mean learning a whole new language. See the XML::DOM package http://search.cpan.org/~tjmather/XML-DOM-1.44/lib/XML/DOM.pm comes as standard with the ActiveState Perl and http://www.w3.org/DOM/. Having used it a couple of times, I would regard the XSLT route as a last resort. I've heard that XSLT2 is even more of a pain to learn and use than XSTL1. Unless you are going to be doing XSLT full-time that is, for small projects scripting I think is best. Client-side xslt, the last I looked and this was a while ago, contained the vagaries of all browsers, and just as much hackery to cope with different implementations of XSLT parsers. XSL subsumes XSLT, but is far more complex. Unless you're using this stuff for proper desktop publishing, I'd be very wary. Roger At 07/05/2006 00:28:27, per...@li... wrote: >Somebody asked off-list about generating HTML reports from unit test >results, possibly using Test::Unit::Runner::XML. Here's the main part >of my reply, in case it's of use to anyone else. > >[...] > >The two routes that spring to mind are > >- write XSL to transform the XML output to HTML > >- use the T:U:Runner::XML module as a template to generate HTML >instead > >I suspect XSL would be easier if you were familiar with both XSL and >Perl, and anyway it's a handy tool to know. From Perl, you can run >xsltproc as a subprocess or go via XML::XSLT. Another route would be >to get the web browser to do the XSLT for you - that would be the >neatest solution. > >http://www.google.co.uk/search?q=client-side+xslt looks promising but >the w3schools link advocates use of ActiveX. I would try >http://www.digital-web.com/articles/client_side_xslt/ . > >This route probably needs less maintenance and also you may find parts >of the Ant(?) project already have something because some of the Java >folks are keen on XSL too. > >Then again if you just want to hack something together and make it >work it may be easier to start with Andrew's perl module. > >[...] > >I guess either solution is about the hundred lines of code mark... > >[...] > > >Matthew #8-) > > >------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >Perlunit-users mailing list >Per...@li... >https://lists.sourceforge.net/lists/listinfo/perlunit-users > |