News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Dagfinn Reiersol's Blog:
Don't refactor without unit tests
September 04, 2009 @ 13:45:59

In a (sort of) response to some of the refactoring posts that Brandon Savage has been posting, Dagfinn Reiersol has suggested something that should have been done from the start - write unit tests before you refactor.

That said, I do have something important to add. The series is missing the first, most basic rule: Don't refactor unless you have good automated test coverage (typically with unit tests). And if there are no test, write them before you start refactoring.

He notes that with successful unit tests in place, you can freely change the underlying structure of the application with (almost) no worries that your application will fall apart the next time it's run. He does point out the need for a bit of refactoring before the tests could really be successfully run (since there's a need for an external twitter connection).

0 comments voice your opinion now!
refactor unittest peerreview


blog comments powered by Disqus

Similar Posts

Mathias Verraes: How Much Testing is Too Much?

Chris Hartjes' Blog: PHPUnit Aborted Fix

Mike Lively's Blog: Adding Database Tests to Existing PHPUnit Test Cases

Stubbles Blog: vfsStream 0.1.0 Released

Jani Hartikainen's Blog: Unit testing 4: Mock objects and testing code which uses the database


Community Events

Don't see your event here?
Let us know!


extension php7 example podcast laravel voicesoftheelephpant library conference api interview version introduction community performance opinion application framework release symfony2 series

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework