nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #02672
[Bug 984264] Re: Assembly Isolation setting is not considered
The setting in question is a default setting. That is, NUnit will run
the tests in the NUnit process _as_a_default. But it's possible to
override the default (for example at the command line) or for the test
assembly itself to require a different setting.
In this case, your tests require .NET 4.0, but the NUnit process is
running under .NET 2.0. It's not possible to run the tests in the same
process in this case, so NUnit starts a separate process. This is as
designed.
It's possible to prevent this behavior by disabling NUnit's automatic
selection of runtimes, but that would not help in this case, since
attempting to load a .NET 4.0 assembly would cause an exception.
It's also possible to force NUnit to run under .NET 4.0, by modifying
the config file. If you do that, then your .NET 4.0 tests will run in
the same process but .NET 2.0 tests will run in a separate process.
In any case, this bug is being closed as "by design."
** Changed in: nunitv2
Status: New => Invalid
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/984264
Title:
Assembly Isolation setting is not considered
Status in NUnit V2 Test Framework:
Invalid
Bug description:
NUnit GUI 2.6.0.12051
Seems that Assembly Isolation level setting is not taken into account.
I have this setting set to "Run tests directly in the NUnit process",
but actually tests are run in a separate process, namely nunit-
agent.exe which is restarted on every test run. This makes hard to
debug tests since previously, one could just set desired breakpoints,
attach to NUnit process and run the required tests.
Important note: The problem is only reproduced if .NET runtime is 4.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/984264/+subscriptions
References