Agile Code Reviews, Part 2

	In my post on agile code reviews, I described how we were
	attacking our code through automated refactorings that we trusted
	to apply without tests. Mostly we applied a series of Extract
	Method refactorings to long methods in the process of performing a
	Compose Method refactoring on the long method. Eventually, your
	team will run out of situations where you can apply automated
	refactorings to improve the design of your code and you'll have
	to start applying actual code changes. Several of the commenters
	on my previous post remarked that making changes without unit
	tests implies risk that can only be averted with sufficient manual
	testing and that such risk is better mitigated by automated tests.
	In this followup post, I'll describe the results from our team at
	applying the decoupling techniques described by Michael Feathers
	to our legacy code so that we could backfill unit tests onto the
	legacy code in preparation for a design change we want to make.

Read the rest here <http://wp.me/pyVNs-eb>

-- 
"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/