Re: [nunitv3] Re: Xsl Transforms and theConsole Runner

HI Aiste,
 
Thanks for the thoughtful reply. Sometimes I don't distinguish
as clearly as I should between the various "NUnits"

There's the NUnit framework that you reference in your tests, 
the runners like nunit-console.exe and nunit.exe and then 
there's the NUnit distribution as a whole. [Not to mention
the coming "NUnit Platform" in version 3.0.]

I feel pretty strongly that transforming xml is not something
that really belongs in nunit-console. One good bit of evidence
for that view is the fact that we would have to duplicate
the code in the gui if we wanted the same capability for the
xml it produces.

But as you point out, folks want something that works and
can be adapted, not something that is left as an "exercise
for the user." So, yes, I think you're right. The transform 
utility belongs in the NUnit distribution, probably along 
with one or two xsl examples.

BTW, I was wrong when I said I hadn't distributed a utility.
I forgot this page...

  http://nunit.org/index.php?p=extras

where the first two items are slightly extended versions of
my simplest utility. The first one does web pages in a fixed
layout. The second allows you to use your own xsl.

I'll put a clean version of at least one of these in the
next NUnit release.

Charlie
  
> -----Original Message-----
> From: Aiste Stikliute [mailto:[email protected]] 
> Sent: Sunday, October 26, 2008 10:18 AM
> To: [email protected]
> Subject: Re: [Nunit-users] [nunitv3] Re: Xsl Transforms and 
> theConsole Runner
> 
> Charlie, I would go for option 3 or 4.
> I have switched from running NUnit GUI manually to nightly 
> tests through NUnit console last week, and the first thing I 
> did was to find a way to automatically apply transformation 
> to the XML results. I wrote a script that would insert this 
> transform line into the TestResult.xml, but as I am not 
> really familiar with scripting, it took me like two hours to 
> decide on how to deal with it and google up the script example.
> My main point is that even though mostly everybody is capable 
> of developing a script that would transform the file, if 
> NUnit would suggest something out of the box (even if that is 
> a separately downloadable utility or a guide how to write one 
> yourself), it would add still one big plus to its usability.
> That's why option 2 (leaving folks to figure out what to do 
> with test results xml) seems unacceptable to me. NUnit is a 
> tool that gives test results in XML, and most of the users 
> transform them sooner or later. Why leave them to figure out 
> their own solution to do that when there can be one nice 
> solution? For the same reason I don't consider option 1 - 
> specifying a transform and then redirecting it to a file is 
> also just a solution some users figured out. Unless it's the 
> recommended way of doing it, I would cut it and give one 
> recommended solution.
> 
> Just my opinion
> -Aiste
> 
> -----Original Message-----
> From: Charlie Poole [mailto:[email protected]]
> Sent: 2008 m. spalio 24 d. 21:56
> To: [email protected]
> Subject: Re: [Nunit-users] [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
>  
> 
> __________ Information from ESET NOD32 Antivirus, version of 
> virus signature database 3556 (20081026) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
>  
> 
> 
> --------------------------------------------------------------
> -----------
> 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=/
> _______________________________________________
> Nunit-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-users
> 



-------------------------------------------------------------------------
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=/