fitSharp
Run Tests With Fitnesse
To run tests from the FitNesse wiki, we need to install FitNesse first. Check the FitNesse download instructions for the latest on how to do that. To customize FitNesse for fitSharp, we add the following definitions to the root page of our tests. This could be the root of our FitNesse wiki (e.g., localhost:8080/root) or on the test page or on a suite page that includes the test pages.

.NET Framework
!define COMMAND_PATTERN {%m -c suiteconfig %p}
!define TEST_RUNNER {pathToFitsharp\Runner.exe}
.NET Core
!define COMMAND_PATTERN {%m pathToFitSharp\Runner.dll -c suiteconfig %p}
!define TEST_RUNNER {dotnet}

where:The Suite Configuration File contains information required to run our tests:Here's an example of a basic Suite Configuration File:
<suiteConfig>
    <System.AppDomainSetup>
        <ConfigurationFile>myapp.config</ConfigurationFile>
    </System.AppDomainSetup>
    <ApplicationUnderTest>
        <AddAssembly>myTests.dll</AddAssembly>
        <AddNamespace>MyTests</AddNamespace>
    </ApplicationUnderTest>
    <Settings>
       <Runner>fitSharp.Slim.Service.Runner</Runner>
    </Settings>
</suiteConfig>
We need to make sure the FitNesse root (e.g., localhost:8080/root) doesn't contain Java paths. If we find the following, we remove them.
!path classes
!path fitnesse.jar
!path fitlibrary.jar
We can now run tests from the FitNesse wiki, or we can run FitNesse tests from the command line with the -c command line argument.

The following is deprecated and may be removed in a future release.

We can specify some of the items in the Suite Configuration File in an alternate way:Example:
!path c:\mypath\myCode.dll
!define COMMAND_PATTERN {%m -r fitnesse.fitserver.FitServer -a myapp.config -c mysuite.xml %p}
!define TEST_RUNNER {c:\apps\fitsharp\Runner.exe}
Copyright © 2018 Syterra Software Inc. All rights reserved.