BDD best practices

Write Gherkin scenarios that a business reader understands without reading the test code. The examples use a webshop with customers, products, carts and orders. Apply the same principles to the vocabulary and observable outcomes of the project you are working on.

Using the rules

• Writing: check each scenario against the rules below before you show it.
• Reviewing: check each scenario against each rule. Before you report a broken rule, read its page in references/. Cite the rule by its number, for example "breaks rule 13".
• A rule marked (smell) asks for an examination, not a fix. Report it as a note.

Each rule links to its explanation and bad and good examples. Read the relevant page when a rule needs clarification. The example steps illustrate wording; they have no bindings. Follow the project's conventions for fixtures, authentication and runner configuration.

Example