Specflow: Rider support

[tenebrarum118]

Would you please take into consideration Rider IDE support. Related jetBrains ticket is here: https://rider-support.jetbrains.com/hc/en-us/community/posts/207696605-Specflow-Add-on

[SabotageAndi]

We talked some time ago about support for it.
But currently we are a very small team that is working in our spare time on SpecFlow. Creating a new integration for another IDE is a lot of work and we have already some other big things (.NET Core, new VS Integration) on our list.

If someone wants to work on it, the current VS Integration is here: https://github.com/techtalk/SpecFlow.VisualStudio
The new VS Integration is here: https://github.com/techtalk/SpecFlow.VisualStudio2

If you have question about the implementation, join us in our Gitter- channel.

[kanekotic]

ok i will do an attempt on this one :), thanks for the good product you guys develop.

if anyone is interested in help is welcome https://github.com/kanekotic/Specflow.Rider

[RapidEU]

Any news?

[SabotageAndi]

@RapidEU no, no new news from us

[kyurkchyan]

This is one of the reasons I can't use Rider as my main IDE. I'd love to see specflow getting it's way through to Rider.

[SabotageAndi]

If we do it, it will take some time until this is done.

In the meantime, Ken Bonny wrote some articles about using SpecFlow in Rider:
https://kenbonny.net/2018/05/28/generating-specflow-files-in-rider/
https://kenbonny.net/2018/07/23/specflow-steps-generation-and-general-rider-changes/

[riezebosch]

But that certainly doesn't work on other platforms (macOS & Linux).

[caetanopaulo]

Hi guys!

First of all congratulations for the great work.
I was wondering if support for Rider on macOS made it to the backlog?

Rider is a great IDE and this is the missing extension.

Keep up with the great work

[ahives]

I think at this point there is no denying that Rider is a top IDE for .NET development. I would say that its second only to Visual Studio now as I write these comments. There is a lot of inertia going in the Rider direction at this point. If I had SpecFlow integration I could completely transition off of VS as Rider is vastly more productive IDE than is VS. Not to mention, it works on my Mac.

[SabotageAndi]

To make it easier for you all to vote on feature requests and influence our prioritization of them in our backlog, we created in our new support tool a special forum to have a better overview of all of them. We moved this feature request there and you can find it here. Sadly we could not take over the existing votes. So if you are still interested in this feature request, please vote again on the new list.

[krishatcher]

@ahives, @caetanopaulo, @riezebosch, @kyurkchyan, @RapidEU, @kanekotic, @tenebrarum118 - upvote new issue here: https://support.specflow.org/hc/en-us/community/posts/360012011397--SpecFlow-Rider-IDE-Support?page=1#community_comment_360003069478

[Andras-Csanyi]

Hi All,
I'm using Specflow with Rider right now. It kind of works fine. Obviously, there is no stepdef and code connection and so on. It is something I can live with.
I recognised one thing which interesting in the implementation. I can't decide whether it should be part of Rider/dotCover or a Specflow plugin.

Rider with continuous testing can recognise which file should be rebuilt when a stepdef file changes. But, it cannot identify which Scenario should be rerun. As a result dotCover is not useful with BDD, however it gives you the automatic build functinality. This is also mentioned in the Rider ticket.

[Enissay]

If we do it, it will take some time until this is done.

In the meantime, Ken Bonny wrote some articles about using SpecFlow in Rider:
https://kenbonny.net/2018/05/28/generating-specflow-files-in-rider/
https://kenbonny.net/2018/07/23/specflow-steps-generation-and-general-rider-changes/

That seems outdated:

• No packages folder in solutions
• I found it C:\Users\<USER>\.nuget\packages BUT it contains no exe files!!

Any clue how to proceed from here ?

[SabotageAndi]

@Enissay the steps from the first blog post are not needed anymore, as the generation is done by the SpecFlow.Tools.MSBuild.Generation nuget package.

[github-actions[bot]]

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.