{"id":1504,"date":"2015-03-16T10:35:12","date_gmt":"2015-03-16T08:35:12","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=1504"},"modified":"2020-01-15T22:03:48","modified_gmt":"2020-01-15T20:03:48","slug":"episode-5-basic-rules-of-refactoring","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2015\/03\/episode-5-basic-rules-of-refactoring\/","title":{"rendered":"Legacy Coderetreat: Episode 5 – Basic Rules of Refactoring – Code Cast"},"content":{"rendered":"

Basic Rules of Refactoring – code cast<\/h2>\n

Blog post series<\/h3>\n

This blog post is part of a series about legacy coderetreat<\/a> and legacy code techniques you can apply during your work. Please click to see more sessions<\/a> about legacy code.<\/p>\n

Code Cast<\/h3>\n

This is a code cast in Java.<\/p>\n

We start by checking what can be extracted to another method. The Basic Rules of Refactoring<\/a> describes the detailed steps I use.<\/p>\n

To ensure that we have a safety net, let us start with covering the code with some system tests and then write tests on the newly created method. These are also characterization tests, but they are often simpler than the system tests we wrote before. When the new method have been covered by tests, call it from the initial place where the code was copied from. Run all the system tests. At the end do some manual testing to see that everything works fine.<\/p>\n

This technique is very useful to have small and safe steps while refactoring. Remember to never cut and paste. Always duplicate the implementation, cover it with tests and then reroute the call to the new code.<\/p>\n

 <\/p>\n