This fix was committed and released with NUnit 2.5.8, but is now being
reactivated.
While ProcessRunner was fixed to reuse the same agent process on reload, it
turns out that higher level code creates an
entirely new ProcessRunner in order when reloading an assembly. This is done
because changed parameters may call for
use of a different type of runner - for example, if the test was loaded in a
separate process but is now to be reloaded in-process.
The implication here is that all runners need to know whether they are
reloading a test or loading it initially, which is a change in the
TestRunner interface.
** Changed in: nunitv2
Status: Fix Released => Triaged
** Changed in: nunitv2
Importance: Medium => High
** Changed in: nunitv2
Milestone: 2.5.8 => None
--
NUnit-agent should be reused on reload
https://bugs.launchpad.net/bugs/612052
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
Status in NUnit V2 Test Framework: Triaged
Bug description:
This issue came up in discussing bug #582051, but is a separate issue.
When tests have been loaded in a separate process under nunit-agent.exe, and the
user reloads the tests after a change, the process is terminated and a new
process
created. If the user had attached to the process for debugging, he will have to
do so all over again with the new process.
It would be more convenient for the user if NUnit simply instructed the existing
process to reload the tests.
_______________________________________________
Mailing list: https://launchpad.net/~nunit-core
Post to : nunit-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nunit-core
More help : https://help.launchpad.net/ListHelp
