#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration
Classic project format using <PackageReference> tags
.feature.cs files are generated using
SpecFlowSingleFileGenerator custom tool
Test Execution Method
Visual Studio Test Explorer
SpecFlow Section in app.config or content of specflow.json
No response
Issue Description
When creating a new feature file, the specflow extension does not make a pending action for the *.feature.cs file (code behind). Therefore, the build will not succeed.
Steps to Reproduce
Action: Create a new feature file with specflow version 3.9.74
Result: No pending action for the .feature.cs file (code behind). Build will not succeed because of missing .feature.cs file
Action: Create a new feature file with specflow version 3.9.69
Result: Pending action for the *.feature.cs file (code behind). Build will succeed
SpecFlow Version
3.9.74
Which test runner are you using?
NUnit
Test Runner Version Number
3.9.74
.NET Implementation
.NET 6.0
Project Format of the SpecFlow project
Classic project format using
<PackageReference>tags.feature.cs files are generated using
SpecFlowSingleFileGenerator custom tool
Test Execution Method
Visual Studio Test Explorer
SpecFlow Section in app.config or content of specflow.json
No response
Issue Description
When creating a new feature file, the specflow extension does not make a pending action for the *.feature.cs file (code behind). Therefore, the build will not succeed.
Steps to Reproduce
Action: Create a new feature file with specflow version 3.9.74 Result: No pending action for the .feature.cs file (code behind). Build will not succeed because of missing .feature.cs file
Action: Create a new feature file with specflow version 3.9.69 Result: Pending action for the *.feature.cs file (code behind). Build will succeed
Link to Repro Project
No response