No Tests found/Invalid Configuration File after adding SpecRun.SpecFlow package

[SabotageAndi]

SpecFlow Version:

• 2.2
• 2.1

Used Test Runner

• SpecFlow+Runner

Version number: 1.6.0

Visual Studio Version

• VS 2017 (15.3.3)

Are the latest Visual Studio updates installed?

• Yes
• No

.NET Framework:

• >= .NET 4
• before .NET 4

Test Execution Method:

• Visual Studio Test Explorer
• TFS/VSTS – Task – PLEASE SPECIFY THE NAME OF THE TASK
• Command line – PLEASE SPECIFY THE FULL COMMAND LINE

Issue Description

When you add one of the NuGet packages SpecRun.SpecFlow, SpecRun.SpecFlow.2-2-0 or SpecRun.SpecFlow.2-1-0 to the project, a Default.srProfile file is added to it.
Some values should be filled in by NuGet. These are projectName, projectId and TestAssemblyPath.
With the latest version of Visual Studio, the values projectName and projectId aren't anymore filled in.

An issue at NuGet is opened for this: NuGet/Home#5880

Workaround

Please fill in the values on your own.
projectName is the name of the project you add the NuGet package.
projectId is the Guid of the project, but you can enter here any valid Guid. You find this by opening your csproj file. There is an element ProjectGuid definded. Take this Guid.

[jgraber]

Hi,
I have the same problem with SpecFlow 2.2.1. The workaround works, but it is hard to find. A fix for this problem would be much appreciated.

Thanks,
Johnny

[SabotageAndi]

The bug is in the NuGet client of Visual Studio. As long as they didn't fix it, we can't do a lot about it. :-/

[Stephen-Mc]

SpecFlow+ Runner 1.6.2 includes a fix for this issue. You now only need to enter a GUID if you are using the SpecFlow+ server (for adaptive test scheduling), as the GUID is used as the unique key for the test results.

[SabotageAndi]

This should be fixed with Visual Studio 2017 15.6. See NuGet/Home#5880 (comment)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.