Hi Stefan...
On the broken xml issues, those seem to be strictly bugs with
nunit-console (in my opinion); bugs would have to be filed with them.
Nunit-console provides these switches that are supposed to control the
output generation and I just don't see the sense in having /xmlConsole
or /transform produce xml results that can't be parsed.
At first I was hoping maybe they were sending the extraneous
stuff to stderr or something, but I redirected that and nope, both the
xml and the stuff that breaks it are coming out stdout.
Then there's the inexplicable (to me) behavior of nunit-console
/transform in that it ignores the output encoding the stylesheet says to
use and substitutes something like "IBM44".
Given that much of the output that breaks the xml is formulaic,
it does seem theoretically possible that <nunit> *could* simply strip
leading output until it sees <?xml when /transform or /xmlConsole are
used, but that seems like make-work to cover over the real problem that
nunit-console does some odd stuff.
Thanks
-Mark
This e-mail message, and any attachments, is intended only for the use of the
individual or entity identified in the alias address of this message and may
contain information that is confidential, privileged and subject to legal
restrictions and penalties regarding its unauthorized disclosure and use. Any
unauthorized review, copying, disclosure, use or distribution is strictly
prohibited. If you have received this e-mail message in error, please notify
the sender immediately by reply e-mail and delete this message, and any
attachments, from your system. Thank you.
-----Original Message-----
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 19, 2006 11:55 PM
To: user@ant.apache.org
Subject: Re: any suggestions how to work with nunit?
Hi Mark,
I'd like to second Steve's request to open bug reports, in fact I've
created enhancement requests for the problems that look easy to solve
and assigned them to myself. That doesn't mean that patches wouldn't
be welcome ;-)
On Tue, 19 Sep 2006, Mark Modrall <[EMAIL PROTECTED]> wrote:
> Nunit-console (which <nunit> wraps) has a number of properties which
> produce broken xml.
What do you suggest the task should do? Have an XML option that would
run nunit-console with /xml and remove the output that makes breaks
the XML structure internally?
> The <nunit> .dotnet plugin supports failOnerror="true" but not
> resultproperty="foo".
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40552>
> I already had to dump <nant> (because it wouldn't use VS 2005
> projects)
Anything we could do from the Ant side here?
> and <msbuild> because it has *neither* failonerror *nor*
> resultproperty.
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40553>
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
