© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
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.