nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Attempting to reproduce your problem, I get passing tests.

Here is the code I used...

using System;
using NUnit.Framework;

namespace ClassLibrary1
{
    [TestFixture]
    public class Class1
    {
        [Test]
        public void Test1() { }
    }
}

Can you explain how yours differs?

Other info that will help resolve this...

Are you creating and opening an assembly or adding a new assembly to
an existing project?
When running the tests are you actually using NUnit or a 3rd party addin?

Charlie

On Mon, Jul 5, 2010 at 11:53 PM, Niklas Winde <niklas.winde@xxxxxxxxx> wrote:
> Public bug reported:
>
> 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.
>
> ** Affects: nunitv2
>     Importance: Undecided
>         Status: New
>
> --
> 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.
>

-- 
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: New

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.