liveBook · Manning

BRIEF

As explained in Effective Behavior-Driven Development

A mnemonic framework of principles for writing clear, maintainable behavior scenarios.

BRIEF is a mnemonic for six principles that help teams write clear, maintainable behavior scenarios: Business language, Real data, Intention revealing, Essential, Focused, and Brief. section 7.2.2

Use the principles to make scenarios easier for the whole team to understand:

  • Business language: use terminology from the business domain to support shared understanding. section 7.2.2
  • Real data: use concrete data when it helps reveal assumptions or edge cases. section 7.2.2
  • Intention revealing: describe what actors aim to achieve, not the mechanics they use. section 7.2.2
  • Essential: remove details that do not illustrate the expected behavior. section 7.2.2
  • Focused: illustrate a single rule in each scenario. section 7.2.2
  • Brief: aim for five steps or fewer so scenarios are easier to read and reason about. section 7.2.2
Table 7.1 BRIEF principles of formulating scenarios
Initial
Principle
Summary
B
Business language
Business terminology aids cross-discipline collaboration
R
Real Data
Using actual data helps reveal assumptions and edge cases
I
Intention revealing
Describe the desired outcomes rather than the mechanism of how they are achieved
E
Essential
Omit any information that doesn’t directly illustrate behavior
F
Focused
Each scenario should only illustrate a single rule
 
Brief
Shorter scenarios are easier to read, understand and maintain

Use the table as a quick reference for the six principles and the purpose of each. section 7.2.2

Keep the rule, remove distractions

A team refining a pay-on-collection scenario spots unrelated steps for searching for a pizza and adding it to a basket. They also question whether the URL and time matter to the rule. The team agrees to clarify the expected behavior first, then address any broken automation separately. section 7.4

How Effective Behavior-Driven Development covers it

How deep it goes
Defines six principles and applies them to scenario cleanup, including a suggested limit of five steps.
Examples
Uses a pizza-order scenario to show how unrelated search, basket, URL, and timing details can distract from a payment rule.
What it assumes
Assumes familiarity with readable Gherkin scenarios and treats writing them well as a skill developed through practice.
What you can do after
Apply the principles to focus scenarios on understandable, single-rule behavior and remove distracting details.
How it connects
Connects Gherkin scenario writing with business collaboration and example mapping.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.