- Fix: GH28: Define Steps produces incorrect regex for step definition
- Find Unused Step Definitions Command: Improved handling of Step Definitions decorated with the 'StepDefinition' attribute. If a Step Definition is used in any Given/Then/When step in a Feature file, the step will no longer show in the 'Find Unused Step Definitions' context menu. (#24)
- Detect existence of SpecFlow for Visual Studio extension and show a warning (#16)
- Fix: Using the extension side-by-side with the SpecFlow for Visual Studio extension causes CompositionFailedException (#25)
Contributors of this release (in alphabetical order): @clrudolphi, @gasparnagy, @UL-ChrisGlew
- Find Unused Step Definitions Command: There is a new command available from within a binding class, "Find Usused Step Definitions". This will list any Step Definition methods that are not matched by one or more Feature steps in the current project. (#8)
- Project template have been updated to the latest Reqnroll and other dependency versions
- Fix: The "Define Steps" command does not abide by the reqnroll.json configuration setting for the
trace/stepDefinitionSkeletonStyle(RegexAttributeorCucumberExpressionAttribute) (#18) - Fix: The "Define Steps" command uses Reqnroll using statements in the generated snipped for SpecFlow projects (#6)
- Fix: "Find Step Definition Usages" command not visible for SpecFlow projects (#7)
- Fix: "Find Step Definition Usages" command fails for first time (#11)
- Support for .NET 8 projects
- New editor command: "Go To Hooks" (Ctrl B,H) to navigate to the hooks related to the scenario
- The "Go To Definition" lists hooks when invoked from scenario header (tags, header line, description)
- Initial release based on v2022.1.91 of the SpecFlow for Visual Studio extension.