This infrastructure works with xunit only currently, but there are multiple options to customize the behavior. Please contact me per email so that we can discuss what would work the best for you.

First thank you for SpecFlow itself we have started using that heavily in our company. I have couple of question how to manage big projects/modules with many steps which are shared between teams but I would like to ask this:

Will it be possible to use SpecFlow without codebehind files without using using xunit as we dont have any “unitTestProvider” in app.config? Right now we generate project-tests.dll files which are executed outside by nunit runner.

We have to double check if this limitation is still there, because I just made a quick tests and it looks like that you can run the tests in parallel, the only thing you cannot do is to configure the test collections that control what can be run in parallel to what. So please check it out and report back the result on GitHub.

“The adapter adds all tests into a single test collection, so they cannot be run parallel.”

Which was a deal breaker sadly, I have my test suite running in parallel and it’s too much effort to switch it back to non-parallel to test this. Other than that, great work, this seems promising. It would be brilliant to see this being rolled out as the ‘standard’ of Specflow itself; no code-behind generation.