search

SpecFlowOSS / SpecFlow.Rider

SpecFlow support for both ReSharper and Rider
MIT License
30 stars 18 forks source link

Add ability to navigate to feature file from unit tests window #37

Open ShinKaiRyuu opened 3 years ago

ShinKaiRyuu commented 3 years ago

Right now navigating from unit tests window lead to nunit generated code instead of Feature file with scenario. @Socolin Is it issue and it will be resolved or this is out of this plugin responseabilty issue? image

Socolin commented 3 years ago

Hello,

Since the Rider test explorer already find the tests by searching for NUnit / XUnit attributes, we don't have much control on that.

I'll take a look if Rider offer some API to do this, I did not see anything so far. Maybe in SpecflowTestExplorer we can remove the test and replace the IUnitTestElement with a new one that encapsulate the other, but it feels a bit hacky. And I don't know what would happen when the NUnitTestExplorer will update the tests.

Socolin commented 3 years ago

Ok so after askin to jetbrains, it seems this is not possible right now.

As a workaround we could add a new navigation to go from/to the test and the generated file (not perfect yet but better than nothing)

I asked Jetbrains if they could change their code to handle this scenario, I'm waiting for their answer.

ShinKaiRyuu commented 3 years ago

@Socolin Hello, any news from JetBrains ? For visual studio we specially added

`

True 
 <DesignTime>True</DesignTime>

`

keys to csproj files to have possibility to move to Test cases from Test Explorer. Without this keys there was message with "No source"

Socolin commented 3 years ago

It should not be there before 2021.3 but here the story if you want to follow: https://youtrack.jetbrains.com/issue/RSRP-484008

ShinKaiRyuu commented 2 years ago

@Socolin any updates on this enchancement?

Socolin commented 2 years ago

@Socolin any updates on this enchancement?

Still waiting after rider to provide us a way to do this. https://youtrack.jetbrains.com/issue/RSRP-484008

jmevel commented 1 year ago

It's been a few weeks I'm testing Rider but yesterday I went back to Visual Studio because of this. So annoying

Thomas-p2-Elliott commented 8 months ago

This messes with my workflow; I have to switch back to VS for projects that use specflow.

GithubOllie commented 1 month ago

Any further updates?

jmevel commented 1 month ago

Any further updates?

SpecFlow is dead, you should use Reqnroll now.

I recreated this issue there