ansaurus

Question

Running NUnit task in CruiseControl.NET always throws errors

Answer 1

+1 A:

This error does not necessarily mean that the problem is with the NUnitCore assembly. It can be that one of the assemblies it needs cannot be accessed. Try turning on Fusion logs - run the fusion log viewer. the logs it will produce will show you more details on whats' wrong.

To run the fusion log viewer open a console window from Visual Studio -> tools menu and type the utility name: fuslogvw

mfeingold 2009-11-08 02:48:55

Answer 2

A:

Question: What are you trying to achieve with this configuration:

<nunit>
  <path>C:\Program Files\NUnit 2.5.2\bin\net-2.0\nunit-console.exe</path>
  <assemblies>
    <assembly>c:\MyTestsPath\bin\Assembly1.dll</assembly>
    <assembly>c:\MyTestsPath\bin\Assembly2.dll</assembly>
    <assembly>c:\MyTestsPath\bin\Assemblyn.dll</assembly>
    <assembly>c:\MyTestsPath\bin\nunit.framework.dll</assembly>
  </assemblies>
</nunit>

Are you trying to unit test nunit.framework.dll? Just guessing, but couldn't this lead to file access problems?

Anyway this leads to more questions:

Are you expecting nunit.framework.dll to be in the compile output folder?
How could it get there?
Did you add it to source control then?
Where do the nunit.framework.dll references in your Visual Studio projects point to?

So many questions although this is supposed to be an answer to your original question.

This is what I would try:

Remove nunit.framework.dll assembly node from CCNET configuration
Let all your Visual Studio unit test projects reference C:\Program Files\NUnit 2.5.2\bin\net-2.0\nunit.framework.dll

The Chairman 2009-11-09 07:03:40

@The Chairman - Sorry I renamed the assembly that I wanted to test to Assembly1.dll. I included c:\MyTestsPath\bin\nunit.framework.dll because when I read up on the NUnit task and it said to reference all the assemblies in the bin of my unit test assembly. I may have read that wrong though. However, I did pull out c:\MyTestsPath\bin\nunit.framework.dll yesterday and the problem still persisted. For the reference in my project. I referenced it from the GAC. You're saying explicilty reference it from it's install folder? Any reason? Is it because on another machine it may not be in the GAC?

nickyt 2009-11-09 14:47:37

Answer 3

+1 A:

I see from the fusion logs that NUnit appears to have ShadowCopy enabled. In the past, I've run into issues with this turned on. It doesn't appear that the CruiseControl task allows switching this off so you may have to call the command line tool directly to do this.

Pedro 2009-11-11 15:25:31

ansaurus

tags:

views:

answers:

Running NUnit task in CruiseControl.NET always throws errors

related questions