49 KiB
Testing REA
Prefer evidence in this order: full end-to-end workflows with real production providers, integration tests across data/API boundaries, then golden regressions from real captured inputs. Keep focused module tests for distinct failure or semantic cases that these workflows cannot reliably reproduce. A test's path or suite name does not establish its behavioral depth.
Avoid tests that mirror getters, enum mappings, fixture helpers, or prescribed call sequences, or assert cache object identity without a caller-visible contract. Prefer representative workflows over a Cartesian matrix when rows cross the same boundary. Retain combinations that exercise a distinct interaction, such as filtering within a full-output envelope. Keep distinct command handlers, producer representations, failure reasons, and lifecycle states c