SpecFlow · Schema
SpecFlow Scenario
Represents a BDD scenario definition in SpecFlow/Gherkin format with all associated metadata
.NETBDDCucumberGherkinTesting
Properties
| Name | Type | Description |
|---|---|---|
| title | string | The scenario title in natural language |
| description | string | Optional description providing additional context for the scenario |
| tags | array | Tags for categorizing and filtering scenarios (e.g., @smoke, @regression, @wip) |
| steps | array | Ordered list of Given/When/Then steps |
| examples | array | Example tables for Scenario Outlines |
| feature | string | Name of the feature this scenario belongs to |
| featureFile | string | Path to the .feature file containing this scenario |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/specflow/main/json-schema/specflow-scenario-schema.json",
"title": "SpecFlow Scenario",
"description": "Represents a BDD scenario definition in SpecFlow/Gherkin format with all associated metadata",
"type": "object",
"properties": {
"title": {
"type": "string",
"description": "The scenario title in natural language"
},
"description": {
"type": "string",
"description": "Optional description providing additional context for the scenario"
},
"tags": {
"type": "array",
"items": {"type": "string"},
"description": "Tags for categorizing and filtering scenarios (e.g., @smoke, @regression, @wip)"
},
"steps": {
"type": "array",
"description": "Ordered list of Given/When/Then steps",
"items": {
"type": "object",
"properties": {
"keyword": {
"type": "string",
"enum": ["Given", "When", "Then", "And", "But"],
"description": "The Gherkin keyword for this step"
},
"text": {
"type": "string",
"description": "The step text in natural language"
},
"dataTable": {
"type": "array",
"description": "Optional data table rows",
"items": {
"type": "array",
"items": {"type": "string"}
}
},
"docString": {
"type": "string",
"description": "Optional multi-line string argument"
}
},
"required": ["keyword", "text"]
}
},
"examples": {
"type": "array",
"description": "Example tables for Scenario Outlines",
"items": {
"type": "object",
"properties": {
"tags": {"type": "array", "items": {"type": "string"}},
"header": {"type": "array", "items": {"type": "string"}},
"rows": {
"type": "array",
"items": {"type": "array", "items": {"type": "string"}}
}
}
}
},
"feature": {
"type": "string",
"description": "Name of the feature this scenario belongs to"
},
"featureFile": {
"type": "string",
"description": "Path to the .feature file containing this scenario"
}
},
"required": ["title", "steps"]
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema 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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/specflow-scenario"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.