legacy code | TestinGil

Gil Zilberfeld explains refactoring legacy code, starting with renaming variables, methods and classes, on the way to easier writing of unit tests.

Legacy Code To Testable Code #1: Renaming

This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring steps before writing tests for legacy code, and how they make our life easier. Other posts include: Renaming is easy and is usually safe refactoring. Most IDEs have the refactoring Read more…

By Gil Zilberfeld, 10 yearsOctober 7, 2014 ago

Gil Zilberfeld introduces a series of posts on refactoring patterns to be used in legacy code, to make it easier for writing unit tests.

Legacy Code To Testable Code: Introduction

The word “legacy” has a lot of connotations. Mostly bad ones. We seem to forget that our beautiful code gets to “legacy code“ status three days after writing it. Michael Feathers, in his wonderful book “Working Effectively With Legacy Code” defined legacy code as code that doesn’t have tests, and Read more…

By Gil Zilberfeld, 10 yearsSeptember 29, 2014 ago