This part of the forum is to vote on future feature requests. When you create a new feature request, please add the product name in front of the title. E.g. [SpecFlow], [SpecMap], ...

specflow error in migration to .net6
0 votes 0 comments
Creating new features files directly in Azure DevOps
1 vote 0 comments
Specflow.Assist support in contains validation for table
3 votes 0 comments
GitHub Actions for SpecFlow+LivingDoc
0 votes 0 comments
Add more placeholders to execution results JSON file name
0 votes 2 comments
[SpecFlow+LivingDoc] Readme/Information page
1 vote 2 comments
Shortcut to autoformat tables in feature files
0 votes 2 comments
Using specflow to run an algorithm instead of test?
0 votes 3 comments
[SpecFlow] Feature file code analyzer
2 votes 0 comments
Allow generator plugins to target .net 6.0
0 votes 1 comment
Updating Newtonsoft.Json in SpecFlow.Plus.LivingDoc.CLI
1 vote 0 comments
SpecRun / SpecFlow+ Runner retirement - Specflow reports replacement
1 vote 2 comments
Support full Github Flavored Markdown in feature Files
0 votes 1 comment
Attach screenshots to TRX reports using Specflow+ Runner Not planned
0 votes 1 comment
Support for Source Code formatting in Doc Strings for SpecFlow+LivingDoc
0 votes 0 comments
Gherkin editor export
2 votes 0 comments
[SpecFlow] An offer concerning adding new TableExtension method
5 votes 0 comments
[Specflow+Runner] Replacement of TestContext (MSTest) in Specflow+Runner Not planned
0 votes 2 comments
Support Feature-level parallel execution for SpecFlow + Runner Not planned
0 votes 2 comments
Support IAsyncDisposable in bindings
1 vote 0 comments
.NET 6 support for the SpecFlow+ Runner Not planned
26 votes 12 comments
[SpecFlow+LivingDoc] Support multiple publishes to LivingDoc (build and release)
8 votes 3 comments
When will a Visual Studio 2022 SpecFlow Extension be available? Completed
1 vote 1 comment
Advanced filtering in living doc
5 votes 1 comment
Allow string arrays as parameters in StepDefinitionBaseAttribute
1 vote 2 comments