Unit tests | TestinGil

Legacy Code to Testable Code #6: Add Overload

This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring […]

This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring

This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring

This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring

This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring

This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring

The word “legacy” has a lot of connotations. Mostly bad ones. We seem to forget that our beautiful code gets

It’s a funny thing, code testability. It’s not really defined, or rather, it is defined poorly. If “testable code” is

Whenever we learn a new skill, and go deeper, it feels like we’re climbing a stairway to mastery. A few