An Examples table supplies the data that turns a Gherkin scenario outline into multiple concrete scenarios. It helps keep similar scenarios readable in one place, while showing the variations that matter. section 8.4 section 8.4.2
The table follows the Examples keyword. Its header names correspond to angle-bracket placeholders in the outline; each non-header row supplies values for one generated scenario. Columns not used as placeholders are ignored, so a description column can explain why an example matters without changing the scenario. section 8.4.2
Listing 8.6 Scenario outline
Scenario Outline: Describe what remains of a pizza
Given a diner cuts their pizza into <slices per pizza> slices
When they eat <slices eaten> slices
Then they should have <remainder> slices left
Examples:
| description | slices per pizza | slices eaten | remainder |
| Not hungry at all | 6 | 0 | all |
| Quite hungry | 6 | 4 | 2 |
| Very hungry | 8 | 8 | none |The pizza example shows three rows producing three scenarios, with a description column providing context for readers. section 8.4.2
Use examples tables to communicate meaningful variations, not simply to accumulate rows:
- Choose examples that clarify distinct behavior; repeated or duplicate rows add little value. section 8.4.3
- Keep tables readable and concise. Large tables with many low-value examples can make patterns hard to spot and slow automation. section 8.4.3

