NUnit-console 2.5.4 cannot run multiple builds?

Question

I'm having problems running tests using the NUnit test runner command line.

I am using version 2.5.4 with .NET 4 on an x64 machine.

Using the following line results in a failure of “Failed to load the file or assembly pane” or one of its dependencies. The system cannot find the specified file. "

nunit-console-x86 foo.dll bar.dll /framework=4.0.30319 

If I canceled the DLL file names, he complains that he will not find "foo" instead ...

This works if I run them separately, for example:

 nunit-console-x86 foo.dll /framework=4.0.30319 

Also, tests of the second file work if I run:

 nunit-console-x86 bar.dll /framework=4.0.30319 

Before upgrading our projects to 4.0, we used NUnit 2.5.2 and the same command-line tool options, and at that moment the runner worked well with several builds. It seems that the ability to run tests on multiple files at the same time is broken ...

Anyone who can see the same behavior or is working, indicating that my environment is somehow disturbed?

/ Per

Answer 1

Build change behavior has changed between 2.5.4 and 2.5.3. This caused problems for us, so we reverted to version 2.5.3 because it still supports framework 4.0.

We use nunit-console.exe 2.5.3 with several assemblies in our msbuild script, which looks like this:

  <Exec Command="%22$(NUnit_Install_Directory)bin\net-2.0\nunit-console.exe%22 /noshadow @(TestableAssemblies, ' ') /xml $(BuildFilesPath)\NUnit-Results.xml" /> 

When executed, it is filled in this way (edited for readability):

"c: \ Program Files \ NUnit 2.5.3 \ bin \ net-2.0 \ nunit-console.exe" / noshadow D: \ BuildAgent \ GojiSoft.Application.Test \ bin \ Release \ GojiSoft.Application.Test. dll D: \ BuildAgent \ GojiSoft.Common.Test \ bin \ Release \ GojiSoft.Common.Test.dll / xml D: \ BuildAgent \ work \ 2f016459feee51ce \ Build \ NUnit-Results.xml

We do not use a 64-bit machine for our unit tests, therefore YMMV.

I have a blog post about an additional modification that you should make to nunit-console-x86.exe.config here: Getting .Net 4.0, Team City, MSBuild and Nunit to play well.

Answer 2

I have the same problem. I got around this by creating a nunit project in a GUI that includes several DLLs. Then I can run it using nunit-console.