# from Dave Rolsky
# on Friday 13 April 2007 09:58 am:
>I'm working on a module/app that will be used to automate testing
> multiple branches of a code base.
...
>Internally so far I've been calling it Test::SmokeRunner, which seems
> like a reasonable name, but I'm open to suggestions.
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"?
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?
--Eric
--
Turns out the optimal technique is to put it in reverse and gun it.
--Steven Squyres (on challenges in interplanetary robot navigation)
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
