SpecFlow → Reqnroll Migration

When to Use

• A .csproj references SpecFlow, TechTalk.SpecFlow, SpecFlow.xUnit, SpecFlow.NUnit, SpecFlow.MsTest, or SpecFlow.Plus.LivingDocPlugin.
• CI uses the stale SpecFlow.Plus.LivingDoc.CLI tool to produce LivingDoc.html.
• The user wants to preserve Gherkin .feature files and existing step definitions while switching to an actively maintained BDD framework.
• Running tests after a partial migration throws Reqnroll.BindingException: ... Alternative may not be empty.

Outcome

A compiling, runnable Reqnroll project that:

• Keeps .feature files and step definitions virtually untouched.
• Usually only needs namespace edits where TechTalk.SpecFlow was imported explicitly; projects using a global <Using Include="TechTalk.SpecFlow" /> often only need that global using switched to Reqnroll.
• Emits an HTML living documentation report via Reqnroll's built-in formatter (no LivingDoc CLI).
• Surfaces BDD test results and a living-doc download link in PRs; deploys gh-pages only on the default branch.

Procedure