Legacy Code to Testable Code #6: Add Overload On Everyday Unit Testing
The post, one in a series of how to make code easierf or unit testing, and somewhat overloaded, now appears on the Everyday Unit Testing site. Check it out!
Category Archives: refactoring
Legacy Code to Testable Code #5: Extract Class
The post, one of a series on making code testable for unit testing is somewhat classy. now appears on the Everyday Unit Testing site. Check it out!
Legacy Code to Testable Code #4: More Accessors! On Everyday Unit Testing
The next post in the “Legacy Code to Testable Code”, somewhat wanting more, is now on the Everyday Unit Testing site. Check it out!
From Legacy Code To Testable Code–Introduction
This post was taken by raiders to the Everyday Unit Testing site. Follow Indy there! It is the starting post about refactoring legacy code in order for unit testing it. http://memecrunch.com/meme/19PWL/exploring-legacy-code
Why We Refactor
Because we know what it is like to read and debug a 500 lines method . And we don’t want to go through it again. Because we’re sure the other guys’ code can use improvement. Even if they thought otherwise. Because we can’t think at the same time about both the solution and its readability.
The Write Stuff
Since this is my blog, I get to showcase things I’ve also written outside it. Don’t worry, it doesn’t mind. Of course, I’m keeping a list of (almost) everything I’ve written under the Publications page. But here are my latest. On the Typemock blog: My first TDD experience A brief history of continuous integration Icy
Skillz
Everyone has skills. According to the dictionary, here’s the definition of Skill: The ability to use one’s knowledge effectively and readily in execution or performance. In other words: ability to do something. Some will say: ability to do something well. In a tweet a while ago, Jim Grenning defined the 3 skills of refactoring: Recognize