test-data-patterns

Create a sealed fluent class with sensible defaults for every field, WithX methods that return this for chaining, and a terminal Build() that returns a fresh production-type instance. Add semantic methods like IsScheduled() for repeated states and coordinated setters for coupled fields.

An Object Mother is a static factory exposing named canonical scenarios, while a Test Data Builder constructs one type with customizable fields. The recommended combination has the Mother take identifying inputs and return a pre-configured Builder the test can further customize.

Use Arrange-Act-Assert as the default for state-based or output-based unit tests. Prefer Given-When-Then when verifying domain behavior, state transitions, or business rules, especially in event-sourced or behavior-oriented codebases where tests should read like specifications.

Skip a builder when a record with one or two fields is constructed directly with named arguments, or when the test is the only place that type is constructed. Builders earn their place with 4+ constructor parameters or construction duplicated across 3+ tests.

Tests calling a many-parameter constructor directly cascade every signature change through the whole suite. Introduce a builder or Arrangement so construction lives in one place; only the Build() or Command property updates when the contract changes.

A mystery guest is a test depending on data created elsewhere, such as shared fixture files or database seeds, hiding the starting state from the reader. Make the Given or Arrange phase explicit in each test, even at the cost of some repetition.