Kirk Brooks writes:. >I just completed a big refactoring of some code...
I read this kind of statements from time to time and wonder what kind of test systems are in place which allow 'big refactoring' efforts to succeed. As developers we'd love to refactor more, but we've found that, at least for our app and our business, the testing costs are too great to justify most refactoring. Even upgrading to a newer version of 4D, which isn't refactoring, but requires similar test coverage, is a major capital expense (>$100K not including 4D licenses). A few weeks ago Jody Bevan mentioned that they periodically 're-write' the base shell that their EMR software is built on. I found that astounding. So what do folks do to verify that their edits didn't break something? Do you have automated tests? How do you ensure 100% coverage? And how do you justify the costs? Tom Benedict Optum This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
