Revision as of 15:33, 30 November 2010 edit 212.150.171.20 (talk) →Which type of testing ensures that refactoring does not change the behavior of the code ← Previous edit		Revision as of 15:34, 30 November 2010 edit undo SineBot (talk \| contribs) Bots 2,564,698 edits m Signing comment by 212.150.171.20 - "→Which type of testing ensures that refactoring does not change the behavior of the code: " Next edit →
Line 38: 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. <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures\|unsigned]] comment added by [[Special:Contributions/212.150.171.20\|212.150.171.20]] ([[User talk:212.150.171.20\|talk]]) 15:33, 30 November 2010 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot--> == Tools ==

Talk:Code refactoring: Difference between revisions