On Fri, 13 Apr 2007, Eric Wilhelm wrote:
If your 'svn up' support and other aspects were configured as pre_smoke
directives in a config, that might make it more easily adaptable than
if the code has to be subclassed to do something different.
Well, it's a little more programmatic than that. Th
# from Dave Rolsky
# on Friday 13 April 2007 11:07 am:
>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).
True, but perhaps that would be a possible execution mode.
# from Dave Rolsky
# on Friday 13 April 2007 10:27 am:
>Yeah, I haven't gotten that far, but it's certainly possible in the
>design. My idea was that a test set could have a custom config file of
>some sort.
Aside: I've just recently started a "Comprehensive Perl Developer Kit",
which is primari
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 "Aut
# 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 s
On Fri, 13 Apr 2007, Andy Lester wrote:
On Apr 13, 2007, at 11:58 AM, Dave Rolsky wrote:
The core idea is that there are multiple "test sets", which is really any
directory that contains a t/ subdirectory with .t files. The app will be a
script you can call from cron to run a test set, and t
On Apr 13, 2007, at 11:58 AM, Dave Rolsky wrote:
The core idea is that there are multiple "test sets", which is
really any directory that contains a t/ subdirectory with .t files.
The app will be a script you can call from cron to run a test set,
and the order is determined by how out of d
I'm working on a module/app that will be used to automate testing multiple
branches of a code base.
The core idea is that there are multiple "test sets", which is really
any directory that contains a t/ subdirectory with .t files. The app will
be a script you can call from cron to run a test s
