Legacy Rescue Pocket Cards
Recall first moves for safely changing legacy code.
No tests There are no tests, so we cannot refactor this. Use when the change is necessary but behavior is unknown. Your response We can start with one characterization fixture from real input and expected current output. That gives the first refactor a tripwire. Do not promise full coverage. Promise one useful observation point. It lowers risk enough to make the first small move. Characterization What does a characterization test protect? The behavior the system currently has, even before the team fully understands whether it is ideal. It is a safety net for refactoring, not a claim that current behavior…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in