What Bug Will It Find?
New post on Everyday Unit Testing, about how we can measure if a test is valuable. Check it out.
Category Archives: legacy code
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!
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!
Legacy Code to Testable Code #3: Adding Setter Accessors On Everyday Unit Testing
The new post, in the “Legacy Code to Tetable Code” on unit testing is somewhat accessible, now on the Everyday Unit Testing site. Check it out!
Legacy Code To Testable Code #2: Extract Method
This post, somewhat painfully, now appears on the Everyday Unit Testing site. It’s about making legacy code easier for unit testing by refactoring the code by method extraction. Check it out!
Legacy Code To Testable Code #1: Renaming
This post, namely, now appears on Everyday Unit Testing. It’s about refactoring legacy code for unit testing by renaming methods and variables. 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