I've found a bug in the NUnit2 test domain. It seems that it changes the current directory to be the directory of the testing assembly, but then tries to use the relative path to access the assembly. I haven't checked it in, because this behavour has changed at some point between 0.8.3 and now. Does anyone need this behaviour? I'm pretty sure it's a bug, but I thought I would check.

Here's the patch (easy fix):

diff -u -r1.10 NUnit2TestDomain.cs
--- NUnit2TestDomain.cs 6 Oct 2003 15:19:56 -0000       1.10
+++ NUnit2TestDomain.cs 29 Oct 2003 19:13:01 -0000
@@ -61,6 +61,7 @@

             string currentDir = Directory.GetCurrentDirectory();
             Directory.SetCurrentDirectory(assemblyDir);
+            assemblyFile = Path.GetFileName(assemblyFile);

             try {
                 RemoteTestRunner runner = CreateTestRunner(domain);

Any objections to this fix?

Matt.



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to