Re: Ambiguous Refactoring Solution

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

> You repeatedly said "Do you write tests for [some] refactoring?" I do
> not write tests for any refactoring. That is not /why/ I write tests.
> I write tests to *prove* deterministically, that the code does what I
> intend it to do.

That's fine for new code development, but the whole context of this
discussion is for legacy code, i.e. existing code that has no tests.
We then discussed some refactoring choices and then the dogma of "no
refactorings without tests!" came out and I raised some examples of
scenarios where that dogma just doesn't make any sense.  I also raised
several examples of where the dogma is sometimes the right advice and
sometimes not.

I'm only saying that judgment and usefuleness (cost/benefit analysis)
trumps dogma.
-- 
"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/