Closed GoogleCodeExporter closed 8 years ago
I've attached a patch that addresses the very particular spot that's in
contention.
I've done no testing other than to verify that the mb-unit solution builds
(including
Icarus and nunit 2.5 integration), and that my test suite will now run
correctly
under both the nunit-gui test runner and Icarus.
This patch is against trunk (revision 1937).
At least one of the relevant places in Nunit 2.5.0.9122 seems to be:
src\NUnitCore\core\TestSuiteBuilder.cs:86
There are probably others. I'm not an NUnit developer. "AutoNamespaceSuites"
seems
to drive whether SetUpFixture's get attached at namespace nodes or not. No
namespace, no way to say when a particular SetUpFixture for a particular would
apply
or should be invoked.
Original comment by storycra...@gmail.com
on 22 Jun 2009 at 8:35
Attachments:
Done in v3.1. Turns out the change was a little more involved than just
turning on
the auto-namespaces flag.
Original comment by jeff.br...@gmail.com
on 18 Jul 2009 at 5:00
Original issue reported on code.google.com by
jeff.br...@gmail.com
on 20 Jun 2009 at 12:40