the defaults - jole78/TeamCity.SpecFlow.Reporting GitHub Wiki
TeamCity.SpecFlow.Reporting is built with conventions, before/over configuration, in mind which means that it assumes a lot of things in order for you to not get lost in configuration hell right away.
However it is important that you have knowledge about the conventions, the defaults, that we're assuming. If you don't like them just change them by overriding one or more of the properties that you see below.
default: Release
This setting controls the configuration that your specflow project is compiled against. We will look for your assembly in the \bin\[Configuration] folder.
default: nunitexecutionreport
This setting controls the type of report that specflow.exe will generate. We think that you're most interested in generating and showing the execution report.
default: true
This settings controls whether or not the output, the generated '.html-report' is added as a build artifact.
default: true
We think you want us to clean up after we have generated the files we need to. That also means that you don't have to use "clean all files before build" or use swabra.
default: [SOLUTION_ROOT]\packages
If the paths to specflow.exe and nunit-console.exe are not provided (overridden) we will look for them inside the packages folder. The setting controls the path to that folder.
[SOLUTION_ROOT] = '..' (one step up in the hierarchy is default on most projects)
default: [SOLUTION_ROOT]\packages\[NUnit-Console Package]
The path to nunit-console.exe.
We will find it in the packages folder but please tell us if you have it stored somewhere else.
default: [SOLUTION_ROOT]\packages\[SpecFlow Package]
The path to specflow.exe.
We will find it in the packages folder but please tell us if you have it stored somewhere else.
Currently you can't change the things mentioned below but you should at least be aware of them.
The SpecFlow executable needs your project file. Default is that we will look for your *.csproj (or *.vbproj) in the same directory as where the script runs from, a.k.a. the 'working directory'
NUnit prefers your project to be compiled. We will look for the compiled assembly using:
[CURRENT_DIRECTORY]\bin\[CONFIGURATION]\[PROJECTFILE_WITHOUTEXTENSION].dll
An example could be: \bin\release\specs.dll (if your project is called specs)
If you use a App.config file for settings, like connection strings and URL:s, make sure you build with correct Configuration, or your settings will not be picked up. If you use the default settings, you need to build in Release for your settings to be picked up. Alternatively, set the Configuration to the configuration you use, most common would be Debug. This is shown in Changing the Defaults.