By piccoloprincipe
via infoq.com
Submitted: Feb 28 2013 / 14:30
Legacy code is stinky. Every decent developer would like to refactor it, and in order to refactor it, one ideally should have a suite of unit test cases to prevent regressions. However, writing unit tests for legacy code is not easy; the legacy code is usually a big mess. To write effective unit tests against the legacy code, you probably need to refactor it first; and to refactor it, you need unit tests to ensure you are not breaking anything. So it is a chicken and egg situation. This article describes a methodology to safely refactor legacy code by sharing a real case I once worked on.
-
Maintaining or Damaging Applications
-
Six Excellent jQuery UI Customizable Themes
-
Live Username and Email Availability Checking using PHP, jQuery and Ajax
-
Major upgrades in performance and usability speed up FlowTraq for network security professionals.
-
Webinar: SQL Query Patterns, Optimized
-
Thread-Safe Queues with ConcurrentQueue
Add your comment
