# from Andy Armstrong
# on Thursday 05 April 2007 02:18 am:
>> I added a concept of "test profiles" to Module::Build
>> for just this sort of thing. You make your gui tests be '.gt'
>> files, your author tests '.at' files, ...
>
>I think I'd rather put my tests into subdirectories to group them
# from Philippe Bruhat (BooK)
# on Thursday 05 April 2007 02:29 am:
>No, I've already solved that problem by putting the tests in separate
>directories. E.g., I've now a single pod.t file in test/pod that
>will use Test::Pod on all the files in cwd (or the files passed as
>command line parameters
Le mercredi 04 avril 2007 à 11:11, Eric Wilhelm écrivait:
>
> Now, the problem you're trying to solve appears to be "run only part of
> the tests". To me, that doesn't involve passing parameters to the
> scripts.
No, I've already solved that problem by putting the tests in separate
directories
On 5 Apr 2007, at 11:01, Eric Wilhelm wrote:
I think I'd rather put my tests into subdirectories to group them -
That only gets you the ability to run some of them at once, not the
ability to *not* run some of them without special action.
You could just
$ runtests -b t/Somedir/*.t t/Otherdir
On 4 Apr 2007, at 18:59, Eric Wilhelm wrote:
# from Andy Armstrong
# on Wednesday 04 April 2007 05:58 am:
runtests t/*.t --select regression,docs
Would select only regression and documentation tests. That's just an
example plucked out of the ether of course - it wouldn't /have/ to
work like
