-
Book Overview & Buying
-
Table Of Contents
Polished Ruby Programming - Second Edition
By :
In general, the process of refactoring existing code is similar to writing code in the first place. In many cases, it's even easier. You can think of new development as writing, and refactoring as editing. For many people, editing is easier than writing. Assuming you've followed the advice in Chapter 11, Testing to Ensure Your Code Works, you already have a good set of tests for the behavior you are refactoring, with either no mocking or minimal mocking. If you've inherited code without tests, or with tests that heavily use mocks and don't give you good confidence that they will catch bugs that can be introduced during refactoring, then, before you start refactoring, the goal should be to get the tests in a good enough shape that you are comfortable they will catch you if you fall. If you refactor some code, and then run the tests and everything passes, and your first thought is, "Maybe I am missing a case where this fails...
Change the font size
Change margin width
Change background colour