nunit-core team mailing list archive

[Niklas Winde <602143@xxxxxxxxxxxxxxxxxx>]

Sure, thank you for your time, sorry I wasted it :(

Niklas

Sent from my iPhone

On 12 jul 2010, at 14.45, Charlie Poole <charlie@xxxxxxxxx> wrote:

> OK - I marked it invalid and closed it for now.
>
> Charlie
>
> ** Changed in: nunitv2
>       Status: New => Invalid
>
> --  
> Running inconclusive tests leaves assembly open
> https://bugs.launchpad.net/bugs/602143
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in NUnit V2 Test Framework: Invalid
>
> Bug description:
> Version 2.5.5.10112
> GUI Runner
>
> I created a new test project in my VS2008 solution.
> I added a few tests without any actual tests in them, just a class  
> and methods with TestFixture and Test attributes respectively. No  
> assertions inside the test methods.
> Running the tests in NUnit reports them as not run or inconclusive  
> and leaves the assembly dll-file open so VS no longer can build.
> Adding assertions to the test methods makes it work.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/nunitv2/+bug/602143/+subscribe

-- 
Running inconclusive tests leaves assembly open
https://bugs.launchpad.net/bugs/602143
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit V2 Test Framework: Invalid

Bug description:
Version 2.5.5.10112
GUI Runner

I created a new test project in my VS2008 solution.
I added a few tests without any actual tests in them, just a class and methods with TestFixture and Test attributes respectively. No assertions inside the test methods.
Running the tests in NUnit reports them as not run or inconclusive and leaves the assembly dll-file open so VS no longer can build.
Adding assertions to the test methods makes it work.