Geekus Con Livus

Malcolm Anderson's home for Geeks With Lives
posts - 63, comments - 51, trackbacks - 23

My Links

News

Archives

Post Categories

FitNesse command line issues with .Net 2.0

There seems to be a small handful of people who are using FitNesse with .Net 2.0 and a smaller handful (me included) are having issues with the fitness command line tool (TestRunner.exe)

 

The error is Type <yourTestTypeName here> could not be found in assemblies.

 

I posted the following comment over at Cory Foy's APress blog in his highly useful entry

Getting up and running with Fitnesse.NET

If anyone else is either having these kind of problems or if you have solved this problem, please let me know.  I'll make sure to post the solution when we find it.

******************************************** Begin Post

We're running the dotnet2 dlls and having an interesting issue.

We have 2 sets of 2 test runs using "Division"

Set1, Test run 1 : Run Division on localhost using the web page and dotnet2\FitServer.exe
Set1, Test run 2 : Run Division on localhost using the command line and dotnet2\TestRunner.exe

Set2, Test run 1 : Run Division on buildserver using the web page and dotnet2\FitServer.exe
Set2, Test run 2 : Run Division on buildserver using the command line and dotnet2\TestRunner.exe

Set1, Test1 : Pass
Set1, Test2 : Pass
Set2, Test2 : Pass
Set2, Test2 : Fails with:
System.ApplicationException: Type 'MyTestNameSpace.Division' could not be found in assemblies.

Is there some kind of permissions issue with the build server that could be causing this issue?

******************************************** End Post

Print | posted on Thursday, May 03, 2007 1:27 PM | Filed Under [ Agile Development Stupid Code Tricks ]

Feedback

Gravatar

# re: FitNesse command line issues with .Net 2.0

I am having the same problem trying to get dotnet2\TestRunner to work with a local server.

Did you find a solution when using it with your build server?
9/12/2007 11:53 AM | Larry Fix
Gravatar

# re: FitNesse command line issues with .Net 2.0

Unfortunately, we never did find a solution that allowed us to use FitNesse.

We solved the problem by using NUnitForms.
9/12/2007 2:09 PM | Malcolm Anderson
Gravatar

# re: FitNesse command line issues with .Net 2.0

Malcom,

Sorry, I don't get emails when there are comments on Apress blog posts.

I just happened to be helping someone else with this when I came across your post. I wonder if you were running the command line from one machine, using Fitnesse on another. In that case, the dll's need to be local to the command line. So if you specify c:\src\bin\my.dll in your Fitnesse page, that needs to exist on your /local/ machine (that is running the command line, *not* your Fitnesse server.

I'm verifying that with the other person right now, and if so, I'll post that to my blog at http://www.cornetdesign.com

- Cory
11/27/2007 11:16 PM | Cory Foy
Gravatar

# re: FitNesse command line issues with .Net 2.0

Hi Cory

I honestly don't know, or remember how we set that up.

Malcolm
12/2/2007 6:45 PM | Malcolm Anderson
Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification:
 

Powered by: