SpecFlow Gherkin Generator

The tool parses Gherkin feature content and generates C# step definitions skeletons aligned to SpecFlow, serving developers, QA engineers, and automation teams. Use cases include bootstrapping a new feature, regenerating stubs after feature updates, and onboarding new teammates to a SpecFlow project. It reduces manual typing, enforces consistent naming, and accelerates onboarding by producing bindable method templates that integrate with existing code. Outputs can target a single feature or an entire suite, preserving namespace and class structure when supplied. It assumes standard Gherkin syntax and SpecFlow bindings, enabling smooth IDE assistance and compilation. It supports basic localization by mapping Gherkin keywords in common languages to internal tokens.
Core Logic & Features: The tool performs feature parsing, identifying Feature, Scenario, Scenario Outline, and Given/When/Then steps; name normalization converts steps to valid C# method names; binding generation creates [Binding] classes with [Given]/[When]/[Then] attributes and skeleton methods; parameter handling detects quoted strings or numeric placeholders and adds typed method parameters; output options produce one or more .cs files or code blocks; configurability allows optional namespace, class name, and code templates; validation ensures identifiers and attributes conform to C# and SpecFlow conventions. Optional enhancements include grouping by feature and templating for reusable code.
Inputs & Outputs: Inputs include feature_content (string), namespace (string, optional), class_name (string, optional), target_version (string, optional), output_format (string, optional). Outputs include generated_code (string) containing .cs skeletons; formatting rules include 4-space indentation, PascalCase method names, and [Binding] attributes. Algorithms & Calculations: The generator uses a parsing stage to extract Feature, Scenarios, and steps, a naming stage to create valid C# identifiers, and a templating stage to emit .cs code with customized namespaces and class names. It recognizes placeholders for parameters and maps them to method parameters; it supports multiple features in one run. Error & Edge Cases: Missing mandatory inputs or invalid Gherkin syntax produce explicit errors; conflicting class names are surfaced; extremely large feature sets may be chunked; external data references are not resolved. Industry/Region & Localization: Gherkin keyword mapping supports common locales; outputs adhere to standard C# coding conventions and SpecFlow binding rules; currency and unit localization are out of scope. Assumptions & Exclusions: Assumes valid Gherkin per spec; excludes runtime test execution, UI integration, and non-C# language code generation.