Re: NUnit 2.5: What's In It Now

"Kelly Anderson" <[email protected]> Mon, 14 Apr 2008 09:53:47 -0600
Newsgroups gmane.comp.windows.dotnet.nunit.devel
Message-ID <[email protected]>
On Sun, Apr 13, 2008 at 12:55 PM, Charlie Poole
<[email protected]> wrote:
> Hi Gary,
>
> Regarding Asserts continuing...
>
>
> Yep, that's what I took Charlie to be suggesting. I think for data-driven
> driven tests this is good for now, but as Charlie says, we could perhaps use
> Assert.Warn(), or as Jeff Brown suggests, could put this into a separate
> context (in an Assert.Multiple() block)
>
> I was thinking of Assert having more than just failures. Right now it has
> Assert.Ignore and Assert.Pass a well.
>
> However, all three of these terminate the test, so it may not be such a good
> idea to put Warn under the
> same heading, unless it is also going to terminate the test. We could have a
> different class that issues
> interim results and messages but continues. That might be clearer to
> everyone.

Perhaps something along the lines of:
NUnit.Framework.Message(???);

-Kelly

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone