Issue with NUnit SetUpFixtureAttribute

Hi.

NCrunch is great but as soon as I implement a class decorated with the SetUpFixtureAttribute including a method decorated with the SetUpAttribute all markers everywhere go black even though NCrunch Processing Queue and NCrunch Tests still execute the tests with "Passed".

    [SetUpFixture]
    public class GlobalFixture
    {
        [SetUp]
        public void GlobalSetUp()
        {
            //Whatever code
        }         
    }

Bye
Andreas

Ok - that's bad!

Can you submit a bug report after this has happened to you? I'd like to take a look at the log file.

Actually don't worry about the bug report - this was pretty easy to reproduce. Fix will be in 1.35b.

This issue should be fixed in the 1.35b build that was released this morning.

I'm running 1.35.0.16b (downloaded this morning) and I'm still seeing this issue.

Hi Mike,

Thanks for posting. Would you be able to submit a bug report using the NCrunch menu? I'm curious about why this issue still exists for you.


Thanks!

Remco

Thanks for sending through the bug report. I'm curious - do the tests work correctly if you turn off the SetupFixture? I'm actually quite amazed that NCrunch is getting as far as trying to run your tests, as right now Silverlight isn't on the list of platforms supported by NCrunch.

SetupFixture is required. We setup some Mocks that are used in many of the tests. Bummer about not supporting Silverlight.

I am having the same issue. I have a SetupFixture which has to setup certain things for integration tests to work, but NCrunch doesn't appear to be running the setup (ReSharper, TestRunner.NET and NUnit GUI / Console do). I am running the latest release (1.40). Any ideas what could still be wrong?

Hi, thanks for posting!

Up until now, I haven't heard reports of this problem resurfacing. Can you provide any details of how you are using SetupFixture? Note that NCrunch will never show code coverage inside the SetupFixture code as it has no active test to associate them with.

Oops your right, NCrunch wasn't wrong. I had test data in the project, but didn't include it in the visual studio project so it wasn't making it to the NCrunch output directory. So just a mistake on myside. Thanks for a great product!