> But what about testing : can you set an efficient unit testing environment > with "in-place" structuration? Certainly. I have had it for years.
> Which steps are necessary to run cactus tests > for example ? Do you think your developpers will go through this steps each > time they modify code ? No and they shouldn't - unless they are VERY patient and have time to kill. You're over doing the whole XP thing if you think you need to run your whole suite of tests every time you change a <td> to a <th> on a jsp page. The point is, for micro-changes, you don't want to run your whole suite of tests. You want instant feedback. I'm now considering changing my directory structure and writing my own webapp plug-in that supports in-place editing. I'm scared however. I wonder how many (as of yet unexplored) webapp-supporting-plugins I'll break in the process. Dave Ford Smart Soft - The Developer Training Company http://www.smart-soft.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
