Fri Feb 8 08:55:55 EST 2008
and we could have it working briefly. What do you think?
Thanks for your help and patience,
On Mon, 24 Jan 2005 17:11:49 -0800, Charlie Poole
<cpoole at pooleconsulting.com> wrote:
> Hi All,
> I'm back to monitoring this list - at least for messages that contain
> "nunit" - and
> I browsed the entire thread to try to understand the problem you're
> trying to deal
> For completeness, I'll list the ways to have a test not run in NUnit:
> 1) Ignore it with IgnoreAttribute
> 2) Ignore it at runtime with Assert.Ignore
> 3) Use CategoryAttribute and exclude the category
> 4) Mark it with the ExplicitAttribute
> 5) Mark it with the PlatformAttribute (2.2.1 and later, I believe)
> 6) Just don't run it - either put it in a separate assembly or don't
> select the
> namespace it lives in to be run.
> 7) Use a filter.
> Items 1 and 2 turn the test yellow, the others don't. Items 3 and 4 can
> overridden in the gui - I don't know about the gtk gui though - without
> any changes to the code. Item 5 is for things you _never_ want to run
> a certain platform, not for bugs you intend to fix. Item 6 seems like a
> of trouble if you are intending to fix something. Item 7 would be
> perfect, if
> we exposed a way for you to do it, but we don't. Internally, we use a
> to implement categories but it's intended to be generic... we just
> there yet.
> So it sounds as if categories are the thing for you right now... maybe
> some use of Platform if you have things that don't work on .NET or that
> you never intend to make work on Mono.
> However, I'm not clear about why you're moving the tests elsewhere while
> they are not being run. Why not just leave them in place?
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
Rafael "Monoman" Teixeira
I'm trying to become a "Rosh Gadol" before my own eyes.
See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment.
More information about the Mono-devel-list