Suite Configuration File
The execution environment for a suite of tests can be controlled by a suite configuration file. This is a way to consolidate configuration information into one place and to remove it from business-facing story tests. We specify the file in the command line for the fitSharp Runner with a -c switch:
pathToFitsharp\runner -c myPath\mysuite.config.xml ...
To specify the file from FitNesse, we include it in the COMMAND_PATTERN definition:
!define COMMAND_PATTERN {%m -c myPath\mysuite.config.xml ...}
The execution environment is re-initialized at the beginning of each test, to preserve test independence. This means any changes made to configurable items during test execution will not be visible to other tests. The exception is the SuiteSetUp page which changes the configuration for all subsequent tests.

The file format is XML, containing configuration items and values grouped into sections:
Here is a sample:
We can also include custom configuration set up by adding nodes in the format:
The sections and configuration items are listed below.

Assemblies and namespaces can be specified to be used when looking for fixture and domain classes.Culture
The culture to use for test execution.FileExclusions
Regular expression patterns can be specified to exclude files from Folder Runner processing.Fit.Operators
Operators can be added or removed from the list of Cell Operators used by Fit.Settings
General configurable items:
These are the behavior keywords:The default behavior is the FitNesse parsing and naming behavior:
.NET Framework only
This section describes the AppDomain in which story tests are executed. Two frequently-used properties are:See the Microsoft documentation for a complete list of properties for AppDomainSetup.

Copyright © 2022 Syterra Software Inc. All rights reserved.