On Fri, 13 Apr 2007, Eric Wilhelm wrote:
I would say it's not really a Test:: module if it doesn't get use()d by tests. Of course, Test::Harness and other harnesses have already invaded, so I suppose history wins again. Is it too late to dub "Tester::" or "TestDriver::" or "RunTests::" or "AutoTest::" (or something) as the home for "things that run tests"?
This had occurred to me as well, and I'd be happy to not use the Test prefix. "SmokeTest(er)?::" seems like another reasonable possibility.
I would like to see "multi" or "sets" in the name. Provided that the svn stuff is not inherent to what you're building, maybe Tester::RunMulti or Tester::RunSets?
Yeah, the SVN piece is a subclass of the core test set functionality, and my theory is others could produce subclasses for other systems.
I think using the words "sets" will be confusing, since that's a term I kind of made up for the app. Multi is a bit better, but might imply parallelization (as in multi-core). I do like the idea of having the name somehow indicate that it's designed to handle many sets of tests, though.
-dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
