nunit-core team mailing list archive

[Petteri Salo <603088@xxxxxxxxxxxxxxxxxx>]

Hi Charlie,

It seems I messed up something with launchpad, email, or something ... .
I got your "Congratulations..." post (2010-07-09) in my email and
responded to it on July the 17th ( see below). I suppose I should
respond from the same email account as the one in my launchpad account.
The mail on the launchpad account are forwarded to the account that I
use at home ... and that is the one I responded from ...

The progress will be slow as I have to survive not being at work, but
watching the kids .... :-)

-Petteri

On July the 17th I said :
Hi Charlie,

I just started my 4 week summer holiday and am not sure how much time
I'll spend at the computer. Anyway, I'll see about fixing the bug
though.

Petteri

-- 
NUnit Gui: Project Config Change from Menu Does Not Change AssemblyWatcher
https://bugs.launchpad.net/bugs/603088
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:
- NUnit 2.5.5.10112
- nunit-x86.exe
- Windows 7 64 Bit.

Create an nunit project with two configurations: Debug and Release. Set each config to load one assembly but from different paths, for example:

win32\debug\some_assembly.dll
win32\release\some_assembly.dll

Save the project, when config is set to debug. Close and re-start nunit-x86.exe, load the project. Then modify your debug dll and observe how it gets reloaded by nunit. Then change the config to release in nunit and modify your release dll so that it should get reloaded by nunit. It does not. Then change the debug dll version again and observe how nunit reloads the assembly even though the config is still release.

I had a look into the sources (2.5.5.10112) and I think the bug is in NUnit.UtilTestLoader class in method NUnit.Util.TestLoader.ReloadTest(), it does not call InstallWatcher() like NUnit.Util.TestLoader.LoadTest() does.

I think ReloadTest and LoadTest methods need refactoring as the code is almost the same.

If someone can advise me how and where to add a unit test for this case, then I could try to do the fix and refactoring myself and post the result.