Revision as of 15:34, 30 November 2010 edit SineBot (talk \| contribs) Bots 2,564,697 edits m Signing comment by 212.150.171.20 - "→Which type of testing ensures that refactoring does not change the behavior of the code: " ← Previous edit		Revision as of 16:41, 30 November 2010 edit undo Mmeijeri (talk \| contribs) Extended confirmed users 5,533 edits →Which type of testing ensures that refactoring does not change the behavior of the code Next edit →
Line 39: 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--> :Frequent full test runs are very useful and using a continuous integration server is a convenient way of doing that. But unit tests can be run after every single refactoring step. If you follow TDD, then it's not something you do only after an hour of refactoring. If you use JUnit Max then it automatically runs your unit tests all the time, in the same way that Eclipse continuously compiles your code and adds squiggly lines as appropriate. [[User:Mmeijeri\|Martijn Meijering]] ([[User talk:Mmeijeri\|talk]]) 16:41, 30 November 2010 (UTC) == Tools ==

Talk:Code refactoring: Difference between revisions