Problem locating fixture when using SetUp block.

[tko...@pictage.com]

I encountered a strange problem that I can't seem to figure out. I
will admit that I'm not master of Linux / Unix systems. I'm going on
faith that everything is installed ok by one of the other guys in my
department. He has Fitnium setup on a Linux box.

I started working toward having everything in a SetUp page in the test
suite. This works fine for me on Windows XP. But when I copied over
my changes to the Linux system they continually fail with this error.
It's a error I've seen many times before.
"Could not find fixture:
com.magneticreason.fitnium.BaseFitniumFixture."

Basically I've tracked it down to this. For whatever reason the Linux
box can't find this fixture when I use it in a SetUp page.
!| com.magneticreason.fitnium.BaseFitniumFixture |

If I just navigate to the SetUp page and run that as a standalone
test, the SetUp works.

For example. If I have the following structure in the test suite...

-SomeTestSuite\
->SetUp
->TearDown
->SomeTestPage\
-->TestCaseOne

TestCaseOne will fail with that error listed above. But running SetUp
by itself will pass.

I'm at the point where I may just have our tech guy move the whole
thing over to a Windows VM. Here's the source of the SetUp page I'm
using.

Sincerely,
Tom
__________________________________________________________________

!path fitnesse.jar
!path fitlibrary.jar
!path .lib/*.jar

!| com.magneticreason.fitnium.BaseFitniumFixture |

|The server is located at | ${seleniumServerName} |
|The server is on port | ${seleniumServerPort} |
|Using the browser | ${testBrowser} | start at | ${serverName} |
|check | is selenium initialised | true |
|set speed to |50| milliseconds |
|set timeout to |50000| milliseconds |
|write to debug | starting test |
|starting at URL | / |
|wait For Page To Load For | 60 | seconds |
|maximise currently selected window |
|set focus to currently selected window |

[tko...@pictage.com]

I think I found out my own problem. My tree structure of my tests was
different between the Linux and Windows box. So this isn't a cross
platform issue. If I take just the following out of the SetUp include
and paste it on every test page it will work.

!path fitnesse.jar
!path fitlibrary.jar
!path ./lib/*.jar
!|com.magneticreason.fitnium.BaseFitniumFixture|

I was hoping I could avoid that. I know it's likely this info won't
change. But I did think that was the propose of the setup block. So
I could add changes in one place and they'll be active in multiple
locations. Still not sure if this is a Fitnesse bug or just poor
judgment on how I have my tests setup. Problem is I have multiple
sites to check. So I'm making many subwikis in my test suite. If
everything is in the parent tree it works fine. But once I use the
SetUp many levels down in the tree the problem starts.