Re: Ambiguous Refactoring Solution

In article <[email protected]>,
    Adam Sroka <[email protected]>  writes:

> I think you may be misunderstanding what I mean when I say to cover
> with tests before you refactor.

No, I don't misunderstand at all.

You didn't really answer any of the questions I posted, but instead
assumed I didn't understand what you were saying.

There are plenty of times where I have enough confidence in automated
refactorings that I don't feel the need to write a covering test
before performing the refactoring.  Rename and Extract Method are the
two most common refactorings used by me, and probably by anyone who
refactors.  With good automated support for these refactorings, I
don't feel I'm "living dangerously" by applying them from my IDE on
code that is uncovered by tests.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>

      Legalize Adulthood! <http://legalizeadulthood.wordpress.com>


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/