7 Tips And Tricks - essenius/FitNesseFitSharpFeatureDemos GitHub Wiki

Using Paths in FitNesse Test Cases

You have seen that this repo (and all other repos here) carefully avoids using absolute paths in the test cases. The only places where absolute paths occur are in plugins.properties and in the Java command to run FitNesse. This is done to make sure that FitNesse tests can be easily moved from one environment to the other. The two mentioned artifacts are setup once per environment and stay constant. The only thing that the test pages still need to know is the location of the fixtures. And of course, the paths of these might differ in different environments. A flexible approach is making sure that these are in the current directory (work folder) – since then no absolute path is needed. For the interactive FitNesse mode, this is done by running FitNesse from the command line, while you are in the directory that contains the fixture. An alternative is to make a fixtures folder, make sure you copy the required fixtures there, and create a desktop shortcut that refers to the fixtures folder as “Start in”.