Re: Test Names in Result File

Hi Stephane,

> I fully agree with the "it would sure be a shame to break 
> people's existing scripts unnecessarily" part.
> 
> I have a reporting system built to accept NUnit XML result 
> files. I would appreciate that it continues to work at least 
> with later 2.X versions.

Point taken. See below regarding the nesting issue in particular.
 
> My comment for future development:
> 
> -Most mapping tools (XSLT editor) are not comfortable with 
> nested types. E.g.. test-suite containing test-suite and so 
> on. A flat list of fully qualified test cases would be easier 
> to build reports upon.

Yes. Although some people would probably complain if we lost
the nesting. Currently, you get either a nested struture or
a flat list, depending on whether you use automatic name spaces.
Are you suggesting it should be flat even when the loaded
test structure was not flat? I could see us losing some
information in that case.

The entire issue of suitability for xsl processing is a bit
of a problem. You see, the primary developer (me), never uses
it, but prefers to write a C# program to read the xml. :-)
Seriously, that means I need to be told what works well for
folks who use XSL.
 
> -Also, the ability to add custom information to this report 
> at run-time would be very valuable for me. I already add 
> custom information via [Property(name, value)] at design 
> time. The same concept for runtime (Log.AddProperty(name, 
> value) for instance) would allow me to consolidate my 
> execution report in one file instead of having my own custom 
> information logging system.

Good idea. By adding a property dynamcally to the test (or
to the result) we could leverage an existing mechanism.

> That's my 2 cents.

Well worth it. :-)

Charlie
 
> Thank you,
> 
> Stéphane
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of Kelly Anderson
> Sent: Tuesday, March 04, 2008 4:20 PM
> To: Charlie Poole
> Cc: [email protected]
> Subject: Re: [nunit-developer] Test Names in Result File
> 
> On Mon, Mar 3, 2008 at 9:26 PM, Charlie Poole 
> <[email protected]> wrote:
> > Hi All,
> >
> >  Currently, we show the full name of a test case in the xml 
> file  but 
> > the simple name without qualifier for suites. This is inconsistent  
> > but expedient, since it allows us to easily display the 
> full names  of 
> > failing test cases. We can, however, manage with either format.
> >
> >  Considering that the result file is used for 
> post-processing, what  
> > do you think would be the best approach here?
> 
> I am not very familiar with the specifics, but in general, I 
> would think the best approach would favor flexibility and 
> ease of use over brevity. That is, if you repeat basically 
> the same information in the XML in two different ways, if 
> that would make post processing scripts easier to write. That 
> would be a good thing, I think. So, if you had one tag 
> containing a partial name, and another containing the full 
> name, people could choose which to use in a particular instance.
> 
> The other thing to keep in mind is that it would sure be a 
> shame to break people's existing scripts unnecessarily.
> 
> -Kelly
> 
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Microsoft Defy all 
> challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> nunit-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-developer
> 
> 
> 
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Microsoft Defy all 
> challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> nunit-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-developer
> 



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/