First, if you are using SpecFlow I would stay on NUnit 2.6.4 instead of going up to NUnit3, the below steps are using SpecFlow 2.1.0 and NUnit 2.6.4 in "C:\NUnit-2.6.4"
If you want the SpecFlow Test Execution Report (STER) in html:
`nunit-console C:\SourceProject\TestProject.dll /out=C:\SpecFlowReport\TestResult.txt /labels`
`specflow nunitexecutionreport C:\SourceProject\TestProject.csproj /xmlTestResult:C:\NUnit-2.6.4\bin\TestResult.xml /testOutput:C:\SpecFlowReport\TestResult.txt /out:C:\SpecFlowReport\SpecFlow_TestExecutionReport.html`
If you want the SpecFlow Step Definition Report:
`specflow stepdefinitionreport C:\SourceProject\TestProject.csproj /out:C:\SpecFlowReport\SpecFlow_StepDefinitionReport.html`
Pickles is also a good and easy way to get a useful view of your tests for team members that maybe do not want to look directly at the code and it also indicates the Pass/Fail status to match the STER of the same test run
Add NuGet "Pickles.CommandLine" 2.16.2 and execute the below from within the resulting package directory to generate the Pickles report files:
`pickles --feature-directory=C:\SourceProject\Features --output-directory=C:\SpecFlowReport\PicklesFeatureReport --link-results-file=C:\NUnit-2.6.4\bin\TestResult.xml --documentation-format=dhtml --enableComments=true
`