Global Install - jole78/TeamCity.SpecFlow.Reporting GitHub Wiki
Introduction
Optionally you might find it handy to install the TSR module globally on the TeamCity agents. This might be a better situation for you if you have many projects that use specflow and you don't want to keep updating them all everytime there's a new version. Or you might just think that the TSR module is a TeamCity thing and shouldn't be mixed up with the source code.
Anyway...here's an alternative.
PSGet
A great way to install modules globally onto you machine is via PSGet. Log onto your TeamCity agents and install PSGet, then you execute:
Install-Module TeamCity.SpecFlow.Reporting -Global
note: that installs the latest TSR module into '*C:\Program Files\Common Files\Modules*' from github.
note2: if you by any chance are executing the TeamCity agent service under a specfic account (not local system) you have to apply the following "fix":
When importing a module, PowerShell refers to an environment variable named PSModulePath which is a list of directories containing PowerShell modules. PowerShell will search through these directories in the order that they are listed in the PSModulePath variable.
So you will have to update the env.PSModulePath variable for your build configuration/s to include the global module location (otherwise the PS runner in TeamCity won't find your module):
value: %env.PSModulePath%;C:\Program Files\Common Files\Modules
PS Runner
OK, now that the TSR module is installed globally we can simplify the PS runner a bit.
Import-Module TeamCity.SpecFlow.Reporting
Invoke-TeamCitySpecFlowReport
The code above assumes that you use all the conventions.
Dependencies
TSR still needs 'nunit-console.exe' to work so if you don't have that somewhere on the build agent and tell TSR about it (PathToNUnitConsoleExe) you still have to include the dependency along with your VS project. Here's how I would have done it:
Your VS project containing the specflow features will probably already have the SpecFlow.NUnit package included. Just add the NUnit.Runners package (it will be a solution-level package though).
...and if you use the 'package-restore' mechanism in TeamCity (NuGet Installer) your build steps will probably look like this:
...just remember to 'update' the TSR package globally sometimes...