Re: Ambiguous Refactoring Solution
hal arnold <[email protected]>
| Newsgroups | gmane.comp.programming.refactoring |
|---|---|
| Message-ID | <[email protected]> |
>> I was a tiny bit surprised to read that you were thinking about
>> refactoring you code when the code didn't yet have any tests.
you wrote:
> It happens all the time. Its what people have been doing for decades.
> Unit tests give you more confidence, but they don't preclude
> refactoring.
It's true that we 'occasionally' have to resort to doing a particular refactoring without the benefit of a test. I would guess that you've come across this idea from reading Feather's book, where he discusses 'seams'. I think he made the point, that it's rare and comes about when you can't figure out a reasonable way to write a focused test first. I can count the times I've had to resort to that; it would be sloth on my part if it happened more often.
regards,
/h
[Non-text portions of this message have been removed]
------------------------------------
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/