SpecFlow C# BDD Tutorial: Complete 2026 Guide

Last updated: June 29, 2026 · Reading time: 9 minutes · By SoftwareTestPilot Editorial Team

What you'll build: A production-ready SpecFlow 3.9 BDD suite in C# / .NET 8, with feature files, step definitions, scenario outlines, typed table transformations, tags, parallel execution, and SpecFlow+ LivingDoc reporting.

SpecFlow is the .NET port of Cucumber. It brings Behavior-Driven Development (BDD) to C# and .NET — same Gherkin syntax, native NUnit / xUnit / MSTest runners, and first-class Visual Studio support.

For deeper background, see our SpecFlow C# automation guide, the BDD Cucumber tutorial, and the SpecFlow interview questions hub.

• .NET 8 SDK or .NET 9 SDK
• Visual Studio 2022 (or JetBrains Rider) with the SpecFlow extension
• C# fundamentals — classes, interfaces, attributes

dotnet new nunit -n SpecFlowDemo
cd SpecFlowDemo

dotnet add package SpecFlow
dotnet add package SpecFlow.NUnit
dotnet add package SpecFlow.Tools.MsBuild.Generation

Create Features/Login.feature:

Feature: User login
  As a registered user
  I want to log in to the application

Scenario: Successful login
  Given I am on the login page
  When I enter "admin@example.com" as the email
  And I enter "Sup3rSecret!" as the password
  And I click the "Sign in" button
  Then I should be on the dashboard page
  And I should see "Welcome, admin"

In Visual Studio, right-click the feature file → Generate Step Definitions. SpecFlow scaffolds a stub class with all step methods.

using NUnit.Framework;
using OpenQA.Selenium;
using OpenQA.Selenium.Support.UI;
using TechTalk.SpecFlow;

namespace SpecFlowDemo.StepDefinitions
{
    [Binding]
    public class LoginSteps
    {
        private readonly ScenarioContext _scenarioContext;
        private IWebDriver _driver;

        public LoginSteps(ScenarioContext scenarioContext)
        {
            _scenarioContext = scenarioContext;
            _driver = (IWebDriver)_scenarioContext["driver"];
        }

        [Given(@"I am on the login page")]
        public void GivenIAmOnTheLoginPage()
        {
            _driver.Navigate().GoToUrl("https://example.com/login");
        }

        [When(@"I enter ""([^""]*)"" as the email")]
        public void WhenIEnterEmail(string email) =>
            _driver.FindElement(By.Id("email")).SendKeys(email);

        [When(@"I enter ""([^""]*)"" as the password")]
        public void WhenIEnterPassword(string password) =>
            _driver.FindElement(By.Id("password")).SendKeys(password);

        [When(@"I click the ""([^""]*)"" button")]
        public void WhenIClickButton(string label) =>
            _driver.FindElement(By.CssSelector("button")).Click();

        [Then(@"I should be on the dashboard page")]
        public void ThenIShouldBeOnTheDashboardPage()
        {
            var wait = new WebDriverWait(_driver, TimeSpan.FromSeconds(10));
            wait.Until(ExpectedConditions.UrlContains("/dashboard"));
            Assert.That(_driver.Url, Does.Contain("/dashboard"));
        }
    }
}

[Binding]
public class Hooks
{
    [BeforeScenario]
    public void BeforeScenario()
    {
        var driver = new ChromeDriver();
        ScenarioContext.Current["driver"] = driver;
    }

    [AfterScenario]
    public void AfterScenario()
    {
        var driver = (IWebDriver)ScenarioContext.Current["driver"];
        driver?.Quit();
    }
}

dotnet test

The NUnit runner discovers and executes the SpecFlow scenarios as standard .NET tests.

Scenario Outline: Login with multiple users
  Given I am on the login page
  When I enter "<email>" as the email
  And I enter "<password>" as the password
  And I click the "Sign in" button
  Then I should see "<greeting>"

Examples:
  | email              | password     | greeting        |
  | admin@example.com  | Sup3rSecret! | Welcome, admin  |
  | viewer@example.com | ViewerPass1! | Welcome, viewer |

The step definitions are unchanged — SpecFlow substitutes the Examples values at runtime.

public class User
{
    public string Email { get; set; }
    public string Password { get; set; }
    public string ExpectedGreeting { get; set; }
}

[Binding]
public class Transformations
{
    [StepArgumentTransformation]
    public IEnumerable<User> TransformUsers(Table table) =>
        table.CreateSet<User>();
}

Feature file:

Scenario: Apply multiple users
  Given I am on the login page
  When I apply the following users:
    | email             | password     | expectedGreeting |
    | admin@example.com | Sup3rSecret! | Welcome, admin   |

Step definition accepts IEnumerable<User> directly — no manual parsing.

@smoke @critical
Feature: Login

@wip
Scenario: Login with SSO

Run by tag:

dotnet test --filter:"TestCategory=smoke"

SpecFlow+ LivingDoc renders human-readable HTML for stakeholders:

dotnet tool install --global SpecFlow.Plus.LivingDoc.CLI
livingdoc test-assembly SpecFlowDemo.dll -t TestExecution.json

Open the generated LivingDoc.html in a browser to browse all features, scenarios, and step results.

Do

• Hold Three Amigos workshops (PM + Dev + QA) before writing Gherkin
• Use declarative language ("I should see…"), not imperative click-by-click steps
• Use scenario outlines for data-driven tests
• Use typed table transformations
• Generate LivingDoc for stakeholders
• Run on every PR via CI

Don't

• Don't put business logic in step definitions — keep them thin
• Don't write imperative scenarios that read like UI scripts
• Don't skip the discovery workshop
• Don't use SpecFlow for unit tests — keep those in xUnit / NUnit
• Don't let your BDD suite become a maintenance burden — prune dead scenarios

1. Reusable step definitions

[Binding]
public class CommonSteps
{
    [Given(@"I am logged in as ""([^""]*)""")]
    public void GivenIAmLoggedInAs(string user) { /* login logic */ }
}

2. Context injection for shared state

[Binding]
public class TestContext
{
    public IWebDriver Driver { get; set; }
    public string CurrentUser { get; set; }
}

3. Parallel execution

[assembly: Parallelizable(ParallelScope.Fixtures)]

Use ThreadLocal<IWebDriver> to avoid driver conflicts across threads.

4. Ordered hooks

[Binding]
public class Hooks
{
    [BeforeScenario(Order = 1)] public void SetupDriver() { }
    [BeforeScenario(Order = 2)] public void SetupTestData() { }
    [BeforeScenario(Order = 3)] public void Login() { }
}

• SpecFlow C# Automation Guide
• BDD Cucumber Tutorial
• SpecFlow Interview Questions
• Selenium WebDriver Guide
• SDET Career Roadmap

Official reference: docs.specflow.org.

Original SoftwareTestPilot research you can cite in reviews, RFCs, and interviews:

• TDD impact benchmarks (2026) — defect density, MTTD, PR test ratio.
• Test pyramid benchmarks (2026) — real 62 / 26 / 12 ratios and flake per layer.
• Shift-left benchmarks (2026) — DORA-style metrics and defect-fix cost.
• Enterprise automation tool benchmarks (2026) — flake vs licence cost.
• Selenium market benchmarks (2026) and Playwright market benchmarks (2026).