SpecFlow.Rider
SpecFlow.Rider copied to clipboard
SpecFlowOSS
Add ability to navigate to feature file from unit tests window
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?
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.
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.
@Socolin Hello, any news from JetBrains ? For visual studio we specially added
<Compile Include="Features\**\*.feature.cs" Visible="false"> <AutoGen>True</AutoGen> <DesignTime>True</DesignTime> </Compile>
keys to csproj files to have possibility to move to Test cases from Test Explorer. Without this keys there was message with "No source"
It should not be there before 2021.3 but here the story if you want to follow: https://youtrack.jetbrains.com/issue/RSRP-484008
@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
It's been a few weeks I'm testing Rider but yesterday I went back to Visual Studio because of this. So annoying
This messes with my workflow; I have to switch back to VS for projects that use specflow.
