I love Specflow. In fact, I rarely write a line of code unless a feature forces me to. It’s a wonderful tool and it’s Visual Studio integration is better than a lot people know. Here are a few things you may not know about.
Go to definition (F12) on a clause will take you straight to that step definition.
Are you running the tests in order to have missing steps generated so you can cut/paste them? This leads to a ton of Pending steps all mixed up and hard to maintain. Hit F12 on the clause you’re going to implement RIGHT NOW instead, and SpecFlow will place the definition, if missing, in your clipboard so you can stick it in the correct place.
Open a feature file and right-click on a single scenario. Choose Run SpecFlow Scenarios and only that specific scenario will be run.
If you’re using SpecFlow for SharePoint development you’ll know that SpecFlow will break your SharePoint features. Once you add a new SP feature, right-click it and clear the custom tool property in the property pane. The broken code-behind will be removed and things will work.
You can set breakpoints in your feature files, just be sure to select Debug SpecFlow Scenarios.
I keep finding new things about this tool, so I’m sure there will be more findings posted.