New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
SabotageAndi opened this Issue Sep 12, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@SabotageAndi
Collaborator

SabotageAndi commented Sep 12, 2017

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

This comment has been minimized.

Show comment
Hide comment
@jgraber

jgraber Sep 20, 2017

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

jgraber commented Sep 20, 2017

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

This comment has been minimized.

Show comment
Hide comment
@SabotageAndi

SabotageAndi Sep 20, 2017

Collaborator

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. :-/

Collaborator

SabotageAndi commented Sep 20, 2017

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

This comment has been minimized.

Show comment
Hide comment
@Stephen-Mc

Stephen-Mc Sep 26, 2017

Collaborator

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.

Collaborator

Stephen-Mc commented Sep 26, 2017

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 comment has been minimized.

Show comment
Hide comment
@SabotageAndi

SabotageAndi Jun 27, 2018

Collaborator

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

Collaborator

SabotageAndi commented Jun 27, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment