Revision as of 00:28, 9 February 2010 edit MassGalactusUniversum (talk \| contribs) Extended confirmed users, Rollbackers 5,472 edits →Redesign (software): new section ← Previous edit		Revision as of 15:33, 30 November 2010 edit undo 212.150.171.20 (talk) →Which type of testing ensures that refactoring does not change the behavior of the code Next edit →
Line 37: == Which type of testing ensures that refactoring does not change the behavior of the code == Unit tests, especially automated ones in the context of test-first or test-driven development, ensure that refactoring does not change the behavior of the code. [[User:Rodasmith\|The Rod]] 18:53, 30 September 2005 (UTC) I find that after refactoring is done, unit testing misses a bunch of ingegrated issues - so do a full run test after refactoring. == Tools ==

Talk:Code refactoring: Difference between revisions