> is useful. (But of course, having a set of tests to confirm that the > refactoring didn't break anything should be a prerequisite to making > that sort of change!
I was thinking the same thing when reading Chiradeeps review on Min's patch. We should start with a set of tests that pass cleanly with the current code before trying changes. > Anyone have other ideas about how to prioritize unit test writing? I think the idea above is good - as well as requiring it for any refactoring in general. --David
