liveBook · Manning

Feature file

A feature file is a human-readable Gherkin document that specifies a software feature and its behavior through scenarios for execution by behavior-driven development tools.

How 5 Manning books explain it

BDD in Action, Second Edition

A feature file is a plain-text Gherkin document that describes one software feature and its scenarios.

How it is used
Groups a feature’s concrete behavioral examples into a readable specification that can be automated.
How deep it goes
Explains titles, descriptions, scenarios, step keywords, tables, naming, and organization; distinguishes an executable specification from a working automated check.
Examples
Uses money transfers, train departures, frequent-flyer points, and capability-based directory layouts to illustrate content and organization.
What you can do after
Practice/perform writing and organizing feature-level Gherkin scenarios, then connect them to automated acceptance tests.

Read how BDD in Action, Second Edition explains feature file →

Effective Behavior-Driven Development

A feature file is a structured text file that expresses a software feature and its behavior scenarios in a format interpretable by BDD tools.

How it is used
Documents coherent business functionality as readable, navigable behavior scenarios.
How deep it goes
Explains the basic file structure, keywords, and organization choices, while referring readers elsewhere for further Gherkin syntax details.
Examples
Uses a delivery-address file and a split between blocklisting and pay-on-collection files to show scenario grouping.
What you can do after
Build it from scratch by naming one coherent feature, grouping related scenarios under rules where useful, and revising files as concerns change.

Read how Effective Behavior-Driven Development explains feature file →

Build Financial Software with Generative AI (From Scratch)

A feature file is a human-readable specification file that declares a behavior-driven development feature and its test scenarios.

How it is used
Defines readable BDD scenarios that connect user requirements to payment parsing and API tests.
How deep it goes
Works through feature scenarios and their executable step definitions, including parameter extraction and response sharing.
Examples
Uses ACH batch header parsing, a GET /files status check, and a Checking application response scenario.
What you can do after
Apply it via pytest-bdd to specify scenarios and connect them to executable step definitions.

Read how Build Financial Software with Generative AI (From Scratch) explains feature file →

Claude at Work

A Gherkin feature file is a text file containing structured behavior scenarios for an application feature.

How it is used
Uses feature files as a review gate for behavior-driven development before implementation proceeds.
How deep it goes
Demonstrates a five-scenario feature file and reviews scenario quality, but does not detail Gherkin syntax.
Examples
Uses a channels feature with signed-in setup and a scenario for creating a public channel.
What you can do after
Evaluate behavior before implementation by reviewing scenarios, correcting gaps, and approving the next build step.

Read how Claude at Work explains feature file →

Shipping Go: Develop, deliver, discuss, design, and go again

A feature file is a text file that specifies software behavior as features and scenarios for a behavior-driven development test runner.

How it is used
Drives behavior-focused integration testing from shared requirements and scenarios.
How deep it goes
Explains Gherkin structure, step mapping, execution, and assertions, but stops short of defining the Gherkin language formally.
Examples
Uses a translation service scenario covering a word, target language, API call, and expected response.
What you can do after
Operate/configure Godog to turn a Gherkin scenario into an application-level test with executable step definitions.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains feature file →

What to know first

Related concepts

Questions about feature file

What is feature file?

A feature file is a human-readable Gherkin document that specifies a software feature and its behavior through scenarios for execution by behavior-driven development tools.

Which Manning books explain feature file?

BDD in Action, Second Edition, Effective Behavior-Driven Development, Build Financial Software with Generative AI (From Scratch), Claude at Work and Shipping Go: Develop, deliver, discuss, design, and go again.

What should I know before learning feature file?

Manning books that teach feature file usually introduce scenario, business rule, capability and integration test first.

What is feature file a kind of?

Feature file is a kind of plain text. Plain text is character data represented without rich formatting, styling, or presentation instructions.

What is feature file part of?

Feature file is part of directory. A directory is a filesystem container for files and possibly other directories, which may itself be nested within another directory.

What are the parts of feature file?

Feature file includes scenario, tag and feature description.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.