liveBook · Manning

Feature file

As explained in Claude at Work

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

A Gherkin feature file records a feature description and behavior scenarios that can be reviewed before implementation. Treat it as a test plan: pause at a defined gate, check scenarios for correctness and completeness, then authorize the next build step. section 6.12 section 6.11

A practical review loop:

  • Generate feature files for implementation slices and label scenarios by slice to keep review in build order. section 6.11
  • Review behavior, not delivery-process notes; correct the feature description and add missing validation scenarios. section 6.8
  • After each slice, deploy the app and run unit and BDD tests; use the scenarios to guide exploratory testing. section 6.11
Listing 6.5 Part of the Gherkin file for the channels feature
@bdd
Feature: Channels

  Conversation in CollabHub happens in channels. A channel belongs to
  exactly one workspace and a public channel is visible to everyone in
  that workspace whether or not they have joined it. Joining is what
  will gate reading messages, from a later slice; it does not gate
  seeing that a channel exists.

  ...

  Background:
    Given Ada is signed in

  Scenario: Ada creates a public channel and lands in it
    When Ada creates a public channel named "general"
    Then Ada is looking at the "general" channel
    And "general" is in Ada's channel list

The channels example shows a feature description, a shared signed-in setup, and a scenario for creating a public channel. section 6.8

How Claude at Work covers it

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.
How it connects
Connects behavior-driven development with implementation slices, unit testing, and acceptance testing.

Also explained in

Compare how 5 books explain feature file →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Claude at Work. The section links point to the parts of the book it draws on.