Project
ReSharper
Priority
Critical
Type
Bug
Fix versions
4.5
State
Fixed
Assignee
Ilya Ryzhenkov
Subsystem
Unit Testing
Affected versions
No Affected versions
Fixed in build
No Fixed in build
  • Created by   Gabor Ratky
    4 years ago (15 May 2007 18:15)
  • Updated by   Gabor Ratky
    2 years ago (08 May 2009 00:26)
  • Jira: RSRP-40575
    (history, comments)
 
RSRP-40575 ReSharper / UnitTestRun ignores classes decorated with the NUnit attribute [SetUpFixture] and does not call SetUp and and TearDown before every TestFixture class
30
Issue is visible to: All Users
  The issue is visible to the selected user group only
UnitTestRunner (and most likely the full blown ReSharper too) ignores [SetUpFixture] classes that are supposed to be called before and after every TestFixture class is ran.

The following code implements a valid NUnit SetUpFixture and should be called:

[SetUpFixture]
public class UnitTestSetUp
{
[SetUp]
public void SetupFixture()
{
Console.WriteLine("I want to be called!");
}

[TearDown]
public void UnitTestTearDown
{
Console.WriteLine("Yeah, me too!");
}
}

Issue was closed
Comments (27)
 
History
 
Linked Issues (?)
 
TeamCity Changes (0)
 
Ilya Ryzhenkov
  Ilya Ryzhenkov
15 May 2007 21:12
4 years ago
This is part of the newer API of NUnit, which is not implemented yet.
Gabor Ratky
  Gabor Ratky
17 May 2007 13:18
4 years ago
Ilya,

Could you give me an estimate as to whether which version will fix and a timeframe that version will be released? I would like to recommend Unit Test Runner for internal usage and then maybe push ReSharper too but this is one feature that existing NUnit tests possibly require.
Ilya Ryzhenkov
  Ilya Ryzhenkov
17 May 2007 15:02
4 years ago
We are not going to support all NUnit 2.4 features in version 3.0. We will work on latest features support after 3.0 release and they will be available in one of the next minor releases or in major release, which is planned somewhere near Orcas release.

As for separate Unit Test Runner, we have no schedule defined for next version of this product yet.
Alison Debreceny
  Alison Debreceny
15 Aug 2007 05:17
4 years ago
This issue appears to be present in TeamCity 2.1 also, making unit tests that require a setup fixture fail.
Lars Corneliussen
  Lars Corneliussen
17 Aug 2007 01:08
4 years ago
Update here? Would be great, if this is supported soon. Can't be so hard, though!?
Brian
  Brian
22 Sep 2007 02:58
4 years ago
This issue also affects ReSharper (ReSharper 3.0.2 C# Edition build 3.0.517.8 on 2007-08-21T09:41:12)
Ken Robertson
  Ken Robertson
05 Dec 2007 23:08
4 years ago
Any update on this? Will it be fixed in the v4.0 release which is supposed to be coming out?
Alexander Kojevnikov
  Alexander Kojevnikov
18 Feb 2008 10:34
3 years ago
This issue is not resolved in the first ReSharper 4.0 EAP build.
William Sorensen
  William Sorensen
20 Mar 2008 21:17
3 years ago
This is an important feature to me; many of the unit tests I run at work use a SetUpFixture to define a local test deck database for the business objects. I can't run any of those with ReSharper.
Sergei Almazov
  Sergei Almazov
02 Apr 2008 13:55
3 years ago
This feature is also important for me, please include it into 4.0
Scott Schecter
  Scott Schecter
10 Apr 2008 20:54
3 years ago
Another vote for supporting [SetUpFixture] without it integration testing is impossible.
Will Shaver
  Will Shaver
18 Apr 2008 03:00
3 years ago
Yet another vote for this being needed! Please include [SetUpFixture] in version 4...
Garth
  Garth
18 Apr 2008 11:26
3 years ago
1 more vote .. definitely need this, making the unit test feature unusable for many cases.
Innomea GmbH
  Innomea GmbH
12 Jun 2008 18:57
3 years ago
Yet another vote.

Please include [SetUpFixture] in a next HotFix.
Marcin Mikołajczak
  Marcin Mikołajczak
08 Jul 2008 19:27
3 years ago
I hope all this voting will make a difference!
Alan Fritz
  Alan Fritz
29 Jul 2008 20:03
3 years ago
SetUpFixture needs to be added ASAP because it makes complicated unit tests much easier to create.
Evgeny Potashnik
  Evgeny Potashnik
28 Aug 2008 07:04
3 years ago
Come on, guys, this is getting ridiculous - the issue has been open for 15 months now! I don't care about the rest of the new NUnit API, whatever it is, but I need this. Surely it can't be that hard to implement?
Luc LEMAIRE
  Luc LEMAIRE
28 Aug 2008 12:42
3 years ago
Let's be clear ... We have evaluated Resharper 6 months ago and found this issue very annoying. We are now wanting for a fix before making a purchase.
Dean Thrasher
  Dean Thrasher
16 Oct 2008 19:50
3 years ago
Add my vote to the total. Please fix this issue.
Gordon Taylor
  Gordon Taylor
17 Oct 2008 00:46
3 years ago
Yeah - SetupTestFixture is really important to us, too - we'd dearly love to see this implemented.
Eric Borman
  Eric Borman
17 Oct 2008 07:24
3 years ago
+1 from us. we use the SetUpTestFixture exclusively.
Adam Nowotny
  Adam Nowotny
17 Oct 2008 21:25
3 years ago
For sln2005 runner you can force to use NUnit 2.4.8 for unit tests. The setup fixture is run then.
carsten wengeler
  carsten wengeler
04 Nov 2008 14:06
3 years ago
How can I force ReSharper to use NUnit 2.4.8?
ReSharper 4.1 still is not able to use the [SetUp] property!
Jamie Ide
  Jamie Ide
30 Jan 2009 04:30
3 years ago
What is the status on this? The lack of support for SetUpFixture is causing us to use the NUnit runner, this after we converted our tests from MS tests to NUnit to take advantage of the ReSharper runner.
Ilya Ryzhenkov
  Ilya Ryzhenkov
30 Jan 2009 20:08
3 years ago
Initial support implemented in 4.5, check nightly builds. Still working on better UI.
Ilya Ryzhenkov
  Ilya Ryzhenkov
09 Feb 2009 21:55
2 years ago
Please advice on UI, if you have any ideas. Like where to put these "setup/teardown" braces in the unit tests views. Note, that they should be nodes, because there could be exceptions, it could take long time to execute, they can have output, etc.
Sean Aitken
  Sean Aitken
08 May 2009 00:26
2 years ago
Someone mentioned that you can "force" the 2.4.8 runner. How?! It is very annoying that I have to hack around this.