There should only be one unless you are using the multiple process setting, then there would be one for each assembly. When reloading, the same process should be reused unless you make changes to settings that require a new process - for example if you change the version of .NET to be used. Even if a new process is needed, the old one should be shut down.
Have you tried this with the latest 2.5.9 snapshot? Charlie On Sun, Nov 14, 2010 at 1:11 AM, Christoph Nahr <673...@bugs.launchpad.net> wrote: > More data: While debugging a unit test with VS2010 with the Attach to > Process feature, I noticed that reloading the test assembly creates > additional nunit-agent processes that stay in memory until the GUI > runner is shut down. There should be only one such process at any given > time, correct? > > -- > nunit.exe session degrades with ever-lengthening "Reloading..." phase when > test project is recompiled > https://bugs.launchpad.net/bugs/673691 > You received this bug notification because you are a member of NUnit > Developers, which is subscribed to NUnit V2. > -- nunit.exe session degrades with ever-lengthening "Reloading..." phase when test project is recompiled https://bugs.launchpad.net/bugs/673691 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: Confirmed Bug description: I'm using nunit to do unit testing for an ASP.NET MVC 2 project. I have a solution with two projects, one being the actual application, and the other being the unit tests. I use the nunit.exe gui to run the unit tests. I invoke the tests by opening up the dll produced by building the project. The first few times everything runs smoothly, with nunit.exe automatically reloading the project when I make changes and rebuild. However, this starts to take a longer and longer amount of time, and eventually, it will get into loop where it says "Reloading..." and the window flickers for a second, says "Reloading...", lather rinse repeat. The behavior is very non-deterministic from what I can observe so far. Sometimes it's fine for ages, sometimes it dies immediately. Perhaps particular change to the project cause massive problems in nunit.exe. I am happy to investigate if someone can point me in the right direction. _______________________________________________ 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
