-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2010-01-05 02:20:20 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2010-01-05 02:20:19 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2010-01-04 02:22:13 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2010-01-03 02:20:27 UTC by sf-robot
-
I will try to come up with a simple reproduce and create a bug report.
2010-01-02 22:13:02 UTC by Jesse Dickey
-
If this were happening, it would be a serious bug, since that's not how NUnit is designed to work. However, I can't reproduce the problem.
Constructors for classes that contain instance members used as test data sources is performed whenever tests are loaded and this may be what you are seeing. Do you have 'Reload on Run' turned on?.
2009-12-31 20:18:05 UTC by charliepoole
-
I know for sure that this happens with the GUI runner. I think it also happens with the console runner because the same thing happens when I run it using TestDriven.NET
What I mean by unrelated TestFixture objects being constructed is that other classes marked as TestFixture from the same project are being constructed. I confirmed this by putting a break point in the constructor of a...
2009-12-31 18:17:47 UTC by Jesse Dickey
-
As a workaround, I suggest using a TestCaseSource located in the fixture or in a separate class. Since TestCaseSource can designate a method, complex initialization can be more easily accomplished. If you use a static method,
no extra object construction takes place.
2009-12-31 04:53:49 UTC by charliepoole
-
I don't fully understand what you are asking for. What do you mean by "other unrelated Test Fixtures"
Also, are you referring to the gui or console runner?.
2009-12-31 04:13:06 UTC by charliepoole
-
Currently you can only initialize instance variables marked with either the Datapoint or Datapoints attribute at their declaration or in the class constructor. Any changes you make to these variables after that do not affect the tests. That is generally a good thing. However it would be nice to be able to initialize these variables in methods marked with the TestFixtureSetup attribute. This...
2009-12-31 01:39:21 UTC by Jesse Dickey
