--- Andy Lester wrote: > I'd throw my hands up and let it go, then. One of the key functions of > Phalanx is to modernize the testing infrastructure of the modules we > touch. If he needs it to stay compatible back to the relative dark > ages, then let's just leave it that way.
Though many modules must remain compatible way back, their Phalanx test suites do not, their primary goal being to test against Ponie. How about the perhaps silly or wild idea of decoupling a module's test suite from the module itself? You could even have multiple test suites for the same module. What triggered this idea is the recent impressive work from Autrijus (Pugs) and Ingy (FreePAN) using a model with committer rights handed out liberally, wiki-style. I could imagine a Phalanx svn respository with all Phalanxers having commit rights, and a free-for-all, where any Phalanxer could write any test for any Phalanx module, always using modern test tools. Low barrier of entry, low communication costs, lots of test duplication perhaps -- but in the testing world, variety and duplication can be your friend. I'm sorry but I don't have the skill or time to provide much practical assistance for such a project but thought I'd throw it out there anyway. /-\ Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com
