A test fixture is an object, database record, or file placed in a known state before a test runs, so the test produces a consistent result. section 3.3
Reuse fixture setup without hiding each test’s assumptions:
- Prefer private factory methods for shared arrange logic; they reduce duplication while keeping setup visible and tests decoupled. section 3.7
- Avoid constructors or setup methods for ordinary shared arrangements because changes can couple every test and obscure its initial state. section 3.3
Visible fixture factories
A purchase test can create `Store store = CreateStoreWithInventory(Product.Shampoo, 10);` and `Customer sut = CreateCustomer();` inside its arrange section, preserving the scenario’s important assumptions.
