scaffolding-tests

Scaffolding tests capture your code's current behavior by recording inputs and outputs to create a golden baseline. Store these snapshots before refactoring, then compare results afterward to detect any regressions or unintended changes in functionality.

A golden master test records actual outputs from your code as a reference baseline, then compares future runs against it to catch behavioral changes. Use it when you're refactoring legacy code or unfamiliar modules where expected behavior isn't fully documented.

Scaffolding tests normalize non-deterministic values like timestamps and random IDs by masking or replacing them before comparison. This ensures golden baselines remain stable and reliable across test runs without false positives from inherently variable data.

Yes. Characterization tests automatically record how legacy code behaves with representative inputs, creating executable documentation of current functionality. This documents expectations and identifies risky areas before planning refactors or test migrations.

Scaffolding tests capture actual current behavior without asserting what's correct, while unit tests verify expected behavior. Use scaffolding first to establish baselines on existing code, then migrate to unit tests with explicit assertions as you refactor.

Yes. After refactoring, run scaffolding tests against your new code and compare outputs to the golden baseline. Any differences signal potential regressions, helping you catch unintended behavioral changes before deployment.