Re: [nunitv3] Re: Xsl Transforms and the Console Runner

Hi All,

I'm forwarding a note I posted on the nunit-discuss list, where
we normally discuss NUnit features. Nobody on that list felt
there was an issue with the change described below, so it's
still in the package.

OTOH, there was significant discussion on this list earlier,
so I'm refloating it here for further discussion if necessary.

I apologize for the multiple nesting, please snip out any
irrelevant context when you reply.

Charlie 

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Charlie Poole
> Sent: Monday, October 20, 2008 2:57 PM
> To: [email protected]
> Subject: [nunitv3] Re: Xsl Transforms and the Console Runner
> 
> 
> Second chance - is it OK with y'all that this feature is gone? :-)
> 
> Charlie 
> 
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Charlie Poole
> > Sent: Saturday, October 11, 2008 11:06 AM
> > To: [email protected]
> > Subject: [nunitv3] Xsl Transforms and the Console Runner
> > 
> > 
> > Hi All,
> > 
> > I'd like your opinions on this feature.
> > 
> > Historically, the nunit console summary was generated by 
> applying an 
> > xsl transform to the xml result file. Users could specify their own 
> > transform and change the appearance of the display.
> > 
> > As I was adding new information, I realized that the console output 
> > was overly coupled to the xml file format by doing it this way. So, 
> > the console summary is now just a bunch of Console 
> writes... so far so 
> > good.
> > 
> > Since this made the /transform command-line option useless, 
> I removed 
> > it.
> > 
> > For most people, that wasn't a problem, but a few folks seem to be 
> > using /transform to send html to the console. I assume they 
> redirect 
> > it to a file in some way. Several folks have asked to have 
> the change 
> > reversed.
> > 
> > If I reverse the change, I will have to remove some of the 
> info that 
> > is now displayed on the console, or add it to the xml file 
> and default 
> > transform. It seems to me that one could just run another program 
> > after NUnit to apply the desired transform to the xml file 
> - which is 
> > still being created.
> > Several folks seem to feel that they can't do it in that 
> way because 
> > of how their CI server works.
> > 
> > I see three options:
> > 
> > 1) Revert to the old behavior - I dislike this because I think the 
> > console output has a purpose of its own, separate from what 
> folks want 
> > to do with html reports.
> > 
> > 2) Leave it as it is and let them figure out how to deal with it. 
> > That's easiest, but may be unpopular in some quarters. :-)
> > 
> > 3) Add put the transform back in, but use it to create an optional 
> > html file through NUnit. I imagine this would satisfy folks, but it 
> > smells a bit to me.
> > 
> > 4) Deliver my own little transformation utility with NUnit 
> - it's so 
> > trivial I haven't ever distributed it, but maybe the objectors just 
> > need a program.
> > 
> > Your advice on this one is appreciated, especially if I've missed 
> > something!
> > 
> > Charlie
> > 
> > 
> > 
> > 
> > > 
> > 
> 
> 
> 
> 
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the 
> Google Groups "NUnit-Discuss" group.
> To post to this group, send email to 
> [email protected] To unsubscribe from this 
> group, send email to [email protected]
> For more options, visit this group at 
> http://groups.google.com/group/nunit-discuss?hl=en
> -~----------~----~----~----~------~----~------~--~---
> 
> 




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/