fitSharp
Folder Runner Basics
This is a description of the basic features of Folder Runner.

namefile systemwithnewfile system

The test files used in the following examples are from Sample Input Files and Sample Output Files.

withfile system
make empty foldertest
make empty foldertest\output
make empty foldertest\output\overidden
alias folderdocument\fitSharp\Fit\SampleOutputFilesasout
alias folderdocument\fitSharp\Fit\SampleInputFilesasin

Folder Runner runs the FIT tests from the files in an input directory and writes the results to an output directory.

withnewfolder runner story
run-c,document\fitSharp\Fit\SampleInputFiles\SampleConfig.$OS$.xml

Test result counts are accumulated for all files processed.

checkresults7 right, 1 wrong, 0 ignored, 0 exceptions

withfile system
ensurefiletest\output\SampleSimpleTest.htmlsame asout\SampleSimpleTest.html
ensurefiletest\output\SampleExcelTest.htmlsame asout\SampleExcelTest.html

Sub-directories are traversed and copied to a matching structure in the output directory.

ensurefiletest\output\SampleSubFolder\SampleFailingTest.htmlsame asout\SampleFailingTest.html

If a file SuiteSetUp.* exists in a folder, it is run before all other files in that folder. SuiteTearDown.* is run after all other files in the folder.

ensurefiletest\output\SampleSubFolder\SuiteSetUp.htmlsame asout\SampleSuiteSetUp.html
ensurefiletest\output\SampleSubFolder\SuiteTearDown.htmlsame asout\SampleSuiteTearDown.html

If a file does not contain any tables, the contents are copied without changes.

ensurefiletest\output\SampleSubNoTest\SampleNoTest.htmlsame asin\SampleSubNoTest\SampleNoTest.html

A file reportIndex.html is created in the output directory with the FIT results of each file processed and links to the output files.

ensurefiletest\output\reportIndex.htmlsame asout\SampleReportIndex.html

A file fit.css is created in the output directories with the styles used by FIT to highlight test results. (This is a bit inconsistent because the test files must already have a link to this stylesheet file.)

ensurefiletest\output\fit.csssame asdocument\fitSharp\fit.css
ensurefiletest\output\SampleSubFolder\fit.csssame asdocument\fitSharp\fit.css

If a file fit.css already exists in the input directory, it is copied to the output directory and not overwritten with the standard version.

ensurefiletest\output\SampleSubWithStyle\fit.csssame asin\SampleSubWithStyle\fit.css

The fit.css file is only creates in sub-directories where test results are written.

notfiletest\output\SampleSubNoTest\fit.cssexists

The input can be a single file. In this case, the suite setup and teardown are not run.

make empty foldertest\output

withnewfolder runner story
run-c,document\fitSharp\Fit\SampleInputFiles\SampleConfig.$OS$.xml ,-i,document\fitSharp\Fit\SampleInputFiles\SampleSubFolder\SampleFailingTest.html

checkresults0 right, 1 wrong, 0 ignored, 0 exceptions

withfile system
notfiletest\output\SampleSubFolder\SuiteSetUp.htmlexists

To process a selected file with the associated suite set up and tear down, use the -s option. This specifies the name of the file, relative to the input folder

make empty foldertest\output

withnewfolder runner story
run-c,document\fitSharp\Fit\SampleInputFiles\SampleConfig.$OS$.xml ,-s,SampleSubFolder\SampleFailingTest.html

checkresults2 right, 1 wrong, 0 ignored, 0 exceptions

XML output can be created.

withnewfolder runner story
run-c,document\fitSharp\Fit\SampleInputFiles\SampleConfigXmlOutput.$OS$.xml

withfile system
ensurefile with pathstest\output\XmlOutput.xmlsame asout\SampleXmlOutput.xml

Files and directories can be excluded.

withnewfolder runner story
run-c,document\fitSharp\Fit\SampleInputFiles\SampleConfig.$OS$.xml,-x,Sample

checkresults0 right, 0 wrong, 0 ignored, 0 exceptions

The output folder can be overridden on the command line.

withnewfolder runner story
run-c,document\fitSharp\Fit\SampleInputFiles\SampleConfig.$OS$.xml,-o,test\output\overridden

withfile system
ensurefiletest\output\overridden\SampleSimpleTest.htmlsame asout\SampleSimpleTest.html
Copyright © 2022 Syterra Software Inc. All rights reserved.