- Fix: Project Templates are broken for .NET Framework (#133)
- Fix: TUnit projects should not include a package reference to Microsoft.NET.Test.Sdk (#134)
Contributors of this release (in alphabetical order): @clrudolphi
- Support file scoped namespace declarations when generating code (#140)
- Improved handling of scope tag expressions, hook and scope errors (#150)
- Improved logging for binding discovery (#154)
- Report generic binding errors and log type load errors of binding discovery (#157)
- Fix: Binding discovery for .NET 10 projects that depend on an ASP.NET project and use the MSDI plugin (#156)
Contributors of this release (in alphabetical order): @304NotModified, @clrudolphi, @gasparnagy
- Renamed to Reqnroll for Visual Studio 2022 & 2026 (#136)
- The 'Define Steps' command honors the StepDefinitionSkeletonStyle setting in the project reqnroll.json configuration file and will generate step skeletons using 'Async' appropriately. (#129)
- Update docs - .NET 10, TUnit, VS2026 (#138)
Contributors of this release (in alphabetical order): @304NotModified, @clrudolphi
- The 'New Project' wizard is updated to use the latest versions of supported test frameworks and .NET frameworks (#113)
- The 'Format Document' command is updated to right-align numeric values in tables. This can be overridden to left align them by setting
gherkin_table_cell_right_align_numeric_content = falsein .editorconfig file within a[*.feature]section. (#107) - Add xunit.v3 as a choice of test framework in the 'New Project' wizard (#120)
- Support for .NET 10 projects (#127)
- Fix: Ambiguous steps reported when definition matches via more than one tag (#95)
- Fix: Incorrect binding language detection for Visual Studio extension (#104)
- Fix: 'New Project' wizard allows specifying project name that results in invalid namespace for generated codebehind (#110)
Contributors of this release (in alphabetical order): @304NotModified, @clrudolphi, @gasparnagy
- Autoformatting replaces repeating
Given/When/Thenkeywords withAndkeyword (#58)
- Fix: The 'FindStepDefinitionUsages' and 'FindUnusedStepDefinitionUsages' commands were not displayed in certain cases (e.g. when implicit usings were enabled) (#68)
Contributors of this release (in alphabetical order): @304NotModified, @clrudolphi, @gasparnagy, @jdb0123
- Suggestion for adding FluentAssertions on the new project wizard screen has been removed to avoid confusions, because FluentAssertion does not offer free use for commercial projects anymore. (#60)
- Show regex options list e.g. '(option1|option2|option3)' parameter in step completion instead of a generic parameter placeholder (#55)
- Added option to use custom binding discovery connectors using the configuration option
ide/bindingDiscovery/connectorPathsetting inreqnroll.jsonconfig file where a custom connector path can be specified. (#63)
- Fix: Error message box when creating feature file with space in its name (#50)
- Fix: Error during discovery of .NET 4 projects when .NET 6.0 is not installed (#53)
- Fix: Bindings cannot be discovered for .NET 4.6.2 projects (#62)
Contributors of this release (in alphabetical order): @gasparnagy, @RikvanSpreuwel
- Added support for .NET 9 through the Visual Studio extension (#44)
Contributors of this release (in alphabetical order): @gasparnagy, @UL-ChrisGlew
- Fix: Reqnroll extension v2024.5.169 fails in Visual Studio 17.8.3 (#42)
Contributors of this release (in alphabetical order): @gasparnagy
- Update dependencies to fix potential security vulnerabilities (#32)
- Bug Fix: Fix 'Reqnroll Extension v2024.3.152 does not work on Visual Studio 17.11.4' by including missing assemblies (#37)
- Bug Fix: Visual Studio 2022 extension "Add New Project" adds dependency for Reqnroll.MsTest 1.0.0 (#41)
Contributors of this release (in alphabetical order): @clrudolphi, @gasparnagy, @UL-ChrisGlew
- HotFix: Revert 'Update dependencies to fix potential security vulnerabilities (#32)' because of compatibility issues with Visual Studio 17.11.4 (#37)
Contributors of this release (in alphabetical order): @gasparnagy
- 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)
- Extend searched config file locations to match the locations searched for the reqnroll runtime (#31)
- Offer language updates of Gherkin v29 in the editor (updated from Gherkin v22) (#33)
- Update dependencies to fix potential security vulnerabilities (#32)
- Fix: Using the extension side-by-side with the SpecFlow for Visual Studio extension causes CompositionFailedException (#25)
- Fix: Define Steps produces incorrect regex for step definition (#28)
Contributors of this release (in alphabetical order): @clrudolphi, @gasparnagy, @jdb0123, @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.