Domain-specific data uses values meaningful in a business domain, even when automation represents them differently. In pizza ordering, a scenario can say “Large” while a step definition receives a PizzaSize enum; built-in conversion can bridge the two. section 14.4
Listing 14.13 Scenario and step definition using built-in enumeration conversion
*** Features/Ordering.feature ***
Rule: More than 4 large pizzas cannot be delivered as a single order
Scenario: Five large pizzas are ordered
...
When the customer places an order for 5 pizzas of size "Large"
*** StepDefinitions/OrderingStepDefinitions.cs ***
[When("the customer places an order for {int} pizza(s) of size {string}")]
public void WhenTheCustomerPlacesAnOrderFor(int count, PizzaSize pizzaSize)
{
var order = new OrderObjectMother()
.WithItems(count, size: pizzaSize)
.Build();
...
}See a scenario that uses the quoted value “Large” and a step definition that receives PizzaSize. section 14.4
Domain measurements and enum values
A scenario can express a large pizza as 14 inches; a manual mapping converts “14\"” to PizzaSize.Large. Alternatively, use the enum value “Large” directly. section 14.4

