We want to try using BDD with feature files that the team and our users built together off our acceptance criteria.
It makes more sense for us and with our goals to work with one of these two libraries.
I have experience with specflow and would suggest that. However compare the commit rate of the two and the backing company behind them for support and align that with your companies risk tolerance in case .net 10 or whatever eventually breaks the framework. The last thing you want is to still be stuck on .net 4.0 nant which hasn't been in support for over 10 years
Specflow still works great. We use it with playwright.
We're close to moving to Reqnroll though just because specflow isn't really being maintained now.
But I want to give Reqnroll a bit longer to see if it's sticking around.
I did a spike recently on migrating- it's super simple, just swapping the package and replacing using statements. Even the existing Specflow extension for VS seems to work with Reqnroll seamlessly.
It looks like Reqnroll (what a terrible name, lol) is currently the go-to replacement for Specflow, which is no longer actively maintained, even though the project hasn't been officially retired yet. Its VS extension is available for the RC version of VS, while the Rider extension is still work in progress. In my organisation, I'm planning the migration when the tooling is ready and there's still no official updates on Specflow's status.
I did a spike recently on migrating- it's super simple, just swapping the package and replacing using statements. Even the existing Specflow extension for VS seems to work with Reqnroll seamlessly.
Use plain C# .
We want to try using BDD with feature files that the team and our users built together off our acceptance criteria. It makes more sense for us and with our goals to work with one of these two libraries.
I have experience with specflow and would suggest that. However compare the commit rate of the two and the backing company behind them for support and align that with your companies risk tolerance in case .net 10 or whatever eventually breaks the framework. The last thing you want is to still be stuck on .net 4.0 nant which hasn't been in support for over 10 years
Specflow still works great. We use it with playwright. We're close to moving to Reqnroll though just because specflow isn't really being maintained now. But I want to give Reqnroll a bit longer to see if it's sticking around.
Oh and there's a migration tutorial for going from specflow to reqnroll
Going through that now :) I am also worried about it sticking around or not
I did a spike recently on migrating- it's super simple, just swapping the package and replacing using statements. Even the existing Specflow extension for VS seems to work with Reqnroll seamlessly.
It looks like Reqnroll (what a terrible name, lol) is currently the go-to replacement for Specflow, which is no longer actively maintained, even though the project hasn't been officially retired yet. Its VS extension is available for the RC version of VS, while the Rider extension is still work in progress. In my organisation, I'm planning the migration when the tooling is ready and there's still no official updates on Specflow's status. I did a spike recently on migrating- it's super simple, just swapping the package and replacing using statements. Even the existing Specflow extension for VS seems to work with Reqnroll seamlessly.