CharliePoole

No, our only crosscutting feature currently is Action Attributes, implemented via ITestAction. We decided to replace it in 3.0 but never got around to a new design, hence it keeps...

@rprouse The idea of a marker attribute was intended as a straw man approach to get some discussion going. The problem I see is that we have been talking for...

Further refinement of the "straw man": Have interfaces, which are intrisically cross-cutting, like `IWrapSetUpTearDown` inherit from `ICrosscutting`. Still just a straw man, however, not an attempt at a design that...

Attributes are important here, but interfaces are the real thing. We know what attributes we have but we don't know what attributes users have created. However, we do know that...

@gilescope Sorry, I can think of several objects that you might want disposed, We do, of course, Dispose the TestFixture instance if it implements IDisposable. Can you be more specific?

@jnm2 Nice list! As a more general suggestion, I'd differentiate between cases where a test __has to__ be run in a particular way and those where it's a decision made...

@marossi7 Any more info on this? If not I will close it. BTW, @OsirisTerje commented that the problem is probably not with the engine, because the vs adapter uses the...

Do you reference the VS adapter? If so, can you run a test removing that reference? That will help to verify that no engine version conflict is occurring.

@rodrigo455 Eliminate NUnit3TestAdapter and try a test run. Ideally, your test project should only have the NUnit reference, so you may consider eliminating all other references except for NUnit temporarily.

Also... where are you invoking code that registers assemblies? Is it located in the SUT or in the test assembly? Are you certain that the registration code is actually invoked...