To execute our tests, we need to tell fitSharp where to find the assemblies that contain our test and production code. There's two ways to do this.

• If we're executing the tests with FitNesse, we can list the assemblies in PATH definitions.

!path c:\myfolder\mytest.dll
!path c:\myfolder\myother.dll

• We can list the assemblies in a Suite Configuration File.

<?xml version="1.0" encoding="utf-8" ?>
<suiteConfig>
  <ApplicationUnderTest>
    <addAssembly>c:\myfolder\mytest.dll</addAssembly>
    <addAssembly>c:\myfolder\myother.dll</addAssembly>
  </ApplicationUnderTest>
</suiteConfig>

We include this file in the COMMAND_PATTERN definition for FitNesse or the command line:

!define COMMAND_PATTERN {%m -c c:\myfolder\mysuite.config.xml ... %p}

or

c:\apps\fitsharp\runner -c c:\myfolder\mysuite.config.xml ...

We can use absolute or relative assembly file names. Relative file names use the standard .NET search algorithm to select the folders to be used. If we need to use other folders to search for assemblies, we can specify a comma-separated list of additional folders to search:

!define COMMAND_PATTERN {%m -f c:\myotherfolder,c:\anotherfolder ... %p}

or

c:\apps\fitsharp\runner -f c:\myotherfolder,c:\anotherfolder ...