SpecFlow · JSON Structure

Specflow Feature Structure

Structure of SpecFlow Feature files and their relationship to Scenarios and Step Definitions

Type: object Properties: 0
.NETBDDCucumberGherkinTesting

SpecFlow Feature is a JSON Structure definition published by SpecFlow.

Meta-schema:

JSON Structure

specflow-feature-structure.json Raw ↑
{
  "name": "SpecFlow Feature",
  "description": "Structure of SpecFlow Feature files and their relationship to Scenarios and Step Definitions",
  "type": "object",
  "fields": [
    {"name": "name", "type": "string", "required": true, "description": "Feature name in natural language"},
    {"name": "description", "type": "string", "required": false, "description": "Business context description"},
    {"name": "tags", "type": "array<string>", "required": false, "description": "Classification tags (@smoke, @regression)"},
    {"name": "background", "type": "Background", "required": false, "description": "Steps that run before each scenario"},
    {"name": "scenarios", "type": "array<Scenario>", "required": true, "description": "List of scenarios in this feature"},
    {"name": "language", "type": "string", "required": false, "description": "Gherkin language code (default: en)"}
  ],
  "relationships": [
    {"resource": "Scenario", "cardinality": "one-to-many", "description": "A feature contains one or more scenarios"},
    {"resource": "StepDefinition", "cardinality": "many-to-many", "description": "Steps are bound to C# step definition methods"},
    {"resource": "Background", "cardinality": "one-to-one", "description": "Optional pre-scenario setup steps"}
  ],
  "children": [
    {
      "name": "Scenario",
      "fields": [
        {"name": "type", "type": "enum", "values": ["Scenario", "ScenarioOutline"], "required": true},
        {"name": "title", "type": "string", "required": true},
        {"name": "tags", "type": "array<string>", "required": false},
        {"name": "steps", "type": "array<Step>", "required": true},
        {"name": "examples", "type": "array<ExampleTable>", "required": false}
      ]
    },
    {
      "name": "Step",
      "fields": [
        {"name": "keyword", "type": "enum", "values": ["Given", "When", "Then", "And", "But"], "required": true},
        {"name": "text", "type": "string", "required": true},
        {"name": "dataTable", "type": "array<array<string>>", "required": false},
        {"name": "docString", "type": "string", "required": false}
      ]
    }
  ]
}

Work with this as data

Every JSON Structure here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This JSON Structure
curl "https://apis.io/api/v1/json-structures/specflow-feature-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.