Overview
Legacy systems often contain behavior that users rely on even when it is surprising or poorly documented. Characterization tests record what the system currently does so refactoring can proceed with fewer accidental changes.
Start with a boundary
Choose a small, valuable workflow and capture representative inputs and outputs. Include edge cases and known defects, but label defects clearly rather than silently treating them as desired behavior.
Refactor in small steps
Add tests, make one structural change, run the relevant suite and review the diff. Keep each step reversible.
Avoid freezing every bug
A characterization test describes current behavior; it does not decide whether that behavior is correct. Agree which behaviors are contractual and which should change through a separate, explicit fix.
Add domain tests over time
As understanding improves, replace broad snapshot-like checks with focused tests that explain the business rule.