liveBook · Manning

Seeded baseline

As explained in Effective Behavior-Driven Development

A test data management approach in which every scenario starts with a standard set of data in the database.

A seeded baseline gives every scenario a standard set of data at the start. Common reference data and default entities are already available, so scenarios need only specify custom entities for the behavior they illustrate. section 18.1 section 18.7

A seeded baseline is one way to prepare a service’s starting state:

  • Unlike a clean start, it includes commonly needed entities rather than starting empty. section 18.1
  • Unlike a snapshot, it provides a basic set of entities rather than a richly populated dataset. section 18.1

Shared starting data

A scenario can use reference data and default entities already in the baseline, then specify only the custom entities needed to show its particular behavior. section 18.1

Figure 18.2 The effort required to automate new scenarios depending on the quantity of data in the baseline

Compare how the effort to automate new scenarios depends on the quantity of data in the baseline. section 18.1

How Effective Behavior-Driven Development covers it

How deep it goes
Defines seeded baselines and contrasts them with clean-start and snapshot baselines.
Examples
Uses reference data and default entities as shared starting data, with custom entities specified per scenario.
What you can do after
Apply it by choosing a common starting dataset when scenarios need shared entities and the approach is feasible.
How it connects
Connects test data management with clean-start and snapshot baselines and with insert, query, and hardcoded approaches.

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.