Re: Ambiguous Refactoring Solution

Hello, Richard.  On Thursday, September 24, 2009, at 4:24:14 PM,
you wrote:

> 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.

Yes, sure. And if that's all you do, you're safe in almost all
cases. How many cases can you think of where an automated rename is
is not safe?

If the refactoring tool has Extract, it's safe unless there's a bug.

And you can get a lot done with extract.

But doing a refactoring without a test isn't quite the same as
refactoring without tests.

Ron Jeffries
www.XProgramming.com
www.xprogramming.com/blog
Agility is not an inescapable law of purity
but a pragmatic principle of effectiveness. -- Marc Hamann



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

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/