On Fri, 17 Jan 2003, Adam Fields wrote: > > I've been reading a lot about the Extreme Programming testing > > framework. I was wandering what experiences, good or bad other > > developers have of developing and maintaining CMS and other Web > > Based apps using this testing technique. Has anybody conciously > > chosen not to go down this route?
I've somehow missed the beginning of this thread... > 2) It's very difficult to run automated testing against UI > components. That's true in general. However for web applications, if you can require XHTML compliance there is an abundance of parsers and tools available to analyze the output. We've put together a successful unit testing strategy this way. For instance, we label important elements with an `id' attribute so the testing framework can examine their contents. > 3) XP pretty much requires that you use an OO language. If you're > using procedural perl or PHP, you're going to run into trouble. I don't follow that... there are certainly advantages of OO tools, but I don't see where that is a specific requirement of XP. The most important refactoring tool is a comprehensive suite of unit tests, in any event. OO languages are orthogonal to good design... they help, but are neither necessary nor sufficient. > 4) XP totally falls apart unless you get complete buy-in from every > part of the team. True, but what process doesn't? -- Jeff Sturm [EMAIL PROTECTED] -- http://cms-list.org/ more signal, less noise.
