Closed jrod567 closed 1 year ago
Closing this - I posted in wrong Repo. Looks like it's already been reported as well: https://github.com/SpecFlowOSS/SpecFlow.VS/issues/127
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.
SpecFlow Version
2022.1.91.26832
Which test runner are you using?
NUnit
Test Runner Version Number
NUnit3TestAdapter 4.2.1
.NET Implementation
.NET 6.0
Project Format of the SpecFlow project
Sdk-style project format
.feature.cs files are generated using
SpecFlow.Tools.MsBuild.Generation NuGet package
Test Execution Method
Visual Studio Test Explorer
SpecFlow Section in app.config or content of specflow.json
{ "$schema": "https://specflow.org/specflow-config.json", "livingDocGenerator": { "enabled": true, "filePath": "myfolder\LivingDoc[PID-{ProcessId}][TID-{ThreadId}]_[{now:MM-dd-yyyy_HH.mm.ss}].json" } }
Issue Description
After updating to Visual Studio v17.5.0, double clicking the feature/test name in Test Explorer no longer takes user to Feature/Scenario. It takes the user to the *.feature.cs codebehind.
In previous versions of Visual Studio (notably, v17.3.1 and v17.3.4), this was not an issue.
Steps to Reproduce
Update to Visual Studio v17.5.0 with SpecFlow extension installed; build project and try to navigate to the feature file from the Test Explorer by double clicking the test name.
Link to Repro Project
No response