Top 25 SpecFlow Interview Questions with Answers (1970) — .NET BDD Edition

SpecFlow is the .NET port of Cucumber. It lets .NET developers write Gherkin feature files and bind them to C# step definitions. See our SpecFlow C# Automation Guide for a full walkthrough.

Behavior-Driven Development is a methodology that uses executable specifications in plain language (Given–When–Then) to align developers, testers, and business stakeholders on what to build.

Gherkin is the plain-text language with the keywords Feature, Scenario, Given, When, Then, And, But. SpecFlow and Cucumber both use the same Gherkin syntax.

• Given — state before the action ("I am logged in").
• When — the action ("I click submit").
• Then — the expected outcome ("I should see…").

A .feature file is a plain-text file written in Gherkin syntax. Place it in the Features/ folder of your project. SpecFlow generates a code-behind file that hooks scenarios into the test runner.

A C# method annotated with [Given], [When], or [Then] and a regex (or cucumber expression) that matches the Gherkin step.

[When(@"I enter ""(.*)"" as the email")]
public void WhenIEnterEmail(string email) { /* ... */ }

Tells SpecFlow that a class contains step definitions or hooks. Required on any class with step methods, otherwise SpecFlow will not discover them.

A template scenario with multiple data sets in an Examples table:

Scenario Outline: Login
  When I enter "<email>" as the email
  Then I should see "<greeting>"
Examples:
  | email             | greeting       |
  | admin@example.com | Welcome, admin |

A table passed to a single step for data-driven scenarios:

When I apply the following codes:
  | code    | discount |
  | WELCOME | 10%      |

Convert a Gherkin table to a typed C# collection:

[StepArgumentTransformation]
public IEnumerable<PromoCode> TransformPromoCodes(Table table) =>
    table.CreateSet<PromoCode>();

Methods that run before/after scenarios, features, or the test run:

[BeforeScenario]
public void BeforeScenario() { /* setup */ }

[AfterScenario]
public void AfterScenario() { /* cleanup */ }

• [BeforeScenario] — runs before every scenario.
• [BeforeFeature] — runs once per feature file.
• [BeforeTestRun] — runs once before the entire suite.

@smoke @critical
Scenario: Login

dotnet test --filter:"TestCategory=smoke"

ScenarioContext lets you share state between steps within one scenario — typically used for the WebDriver instance, test data, or anything that has to cross step boundaries. Prefer context injection over static fields for thread safety.

Reqnroll is a 2024 community fork of SpecFlow. For greenfield projects, evaluate both. For existing SpecFlow projects, stay on SpecFlow unless you have a concrete reason (e.g. faster release cadence) to migrate.

A tool that generates human-readable HTML documentation from feature files. It publishes the executable specification of your system — perfect for stakeholders who don't read code.

Right-click the .feature file → Generate Step Definitions. SpecFlow creates a stub class with each step as a method to implement.

SpecFlow 3.9+ supports NUnit, xUnit, and MSTest. NUnit is the most popular choice in .NET QA shops in 2026.

Use [StepArgumentTransformation] to convert Gherkin arguments to typed values:

[StepArgumentTransformation(@"(\d+) days ago")]
public DateTime DaysAgo(int days) => DateTime.UtcNow.AddDays(-days);

Use the SpecFlow context-injection pattern. Create a POCO context class and inject it into step classes via constructor — SpecFlow's container resolves the same instance per scenario.

Yes — via NUnit's [Parallelizable] attribute. SpecFlow parallelises at the feature-file level by default. Make sure WebDrivers and contexts are per-scenario (no statics).

Use a Background step or a custom hook to log in once per scenario:

Background:
  Given I am logged in as "admin@example.com"

Create a DriverFactory that returns an IWebDriver, store it in ScenarioContext, and inject it into step definitions via constructor. See our Selenium Q&A bank for related patterns.

SpecFlow 3.9.x supports .NET 6, 7, 8, and 9. Use the latest 3.9.x release for the best .NET 8/9 experience.

Same Gherkin syntax, different binding languages. SpecFlow = C#/.NET. Cucumber-JVM = Java. Scenarios written in one can be ported to the other with minimal effort.