This allows you to specify a regex pattern to filter the test file list with.
Ie:
harness -v -re \bop\b \bext\b
would run all op and ext tests listed in the manifest in verbose.
harness -v -re=y op\*.t
would run all test files with a patch with 'y' in them that are in op\*.t
This is works usefully with the Makefile patch i sent in.
Cheers,
Yves
--
First they ignore you, then they laugh at you, then they fight you,
then you win.
+Gandhi
diff -wurd ./t/harness g:\blead_trie/t/harness
--- ./t/harness=092004-10-31 17:07:37.000000000 +0100
+++ g:\blead_trie/t/harness=092005-02-18 20:20:06.379105600 +0100
@@no-spam -54,6 +54,16 @@no-spam
return map {$_, 1} split /\s+/, $_[0];
}
=20
+if ($ARGV[0]=3D~/^-re/) {
+ if ($ARGV[0]!~/=3D/) {
+ shift;
+ $re=3Djoin "|",@no-spam
+ @no-spam
+ } else {
+ (undef,$re)=3Dsplit/=3D/,shift;
+ }
+}
+
if (@no-spam {
if ($^O eq 'MSWin32') {
=09@no-spam =3D map(glob($_),@no-spam
@@no-spam -108,6 +118,8 @@no-spam
if ($^O eq 'MSWin32') {
s,\\,/,g for @no-spam
}
+@no-spam /$re/, @no-spam
+ if $re;
Test::Harness::runtests @no-spam
exit(0) unless -e "../testcompile";
=20
=20
[qptext harness.patch]
demerphq wrote:
>This allows you to specify a regex pattern to filter the test file list with.
>
>Ie:
>
> harness -v -re \bop\b \bext\b
>
>would run all op and ext tests listed in the manifest in verbose.
>
> harness -v -re=y op\*.t
>
>would run all test files with a patch with 'y' in them that are in op\*.t
>
>This is works usefully with the Makefile patch i sent in.
>
Thanks. Applied to bleadperl as change 23993.
- Steve
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
demerphq wrote:
>On Wed, 23 Feb 2005 14:03:39 +0000, Steve Hay <steve.hay@no-spam> wrote:
>
>
>>demerphq wrote:
>>
>>
>>
>>>This allows you to specify a regex pattern to filter the test file list with.
>>>
>>>Ie:
>>>
>>> harness -v -re \bop\b \bext\b
>>>
>>>would run all op and ext tests listed in the manifest in verbose.
>>>
>>> harness -v -re=y op\*.t
>>>
>>>would run all test files with a patch with 'y' in them that are in op\*.t
>>>
>>>This is works usefully with the Makefile patch i sent in.
>>>
>>>
>>>
>>Thanks. Applied to bleadperl as change 23993.
>>
>>
>
>Hi, attached patch adds a bit to perlhack.pod about the new options,
>and cleans up a bit of the make target documentation.
>
Thanks. Applied as change 23995 (with a couple of minor tweaks).
- Steve
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
Forgot to include the list on this....
On Thu, 24 Feb 2005 11:48:02 +0100, H.Merijn Brand <h.m.brand@no-spam> wrote:
> On Wed, 23 Feb 2005 17:49:50 +0100, demerphq <demerphq@no-spam> wrote:
> > Hi, attached patch adds a bit to perlhack.pod about the new options,
> > and cleans up a bit of the make target documentation.
>
> You're quite rigid here in the statements about win32:
>
> +(Not available on Win32)
> +
>
> There's no "todo" about this. Is it indeed as stated, or is
>
> + (Not yet available on Win32)
> +
>
> more appropriate?
Actually i think both would apply depending on the actual target you
mean. (Consider that valgrind isnt going to work on Win32) I also
suspect that I forgot to send through a patch to win32/makefile.mk and
win32/Makefile which were meant to accompany the doc patch. Im just
resync'ing now so ill follow up on this later.
Yves
--
First they ignore you, then they laugh at you, then they fight you,
then you win.
+Gandhi
On Thu, 24 Feb 2005 18:26:49 +0100, demerphq <demerphq@no-spam> wrote:
> Forgot to include the list on this....
>
> On Thu, 24 Feb 2005 11:48:02 +0100, H.Merijn Brand <h.m.brand@no-spam> wrote:
> > On Wed, 23 Feb 2005 17:49:50 +0100, demerphq <demerphq@no-spam> wrote:
> > > Hi, attached patch adds a bit to perlhack.pod about the new options,
> > > and cleans up a bit of the make target documentation.
> >
> > You're quite rigid here in the statements about win32:
> >
> > +(Not available on Win32)
> > +
> >
> > There's no "todo" about this. Is it indeed as stated, or is
> >
> > + (Not yet available on Win32)
> > +
> >
> > more appropriate?
>
> Actually i think both would apply depending on the actual target you
> mean. (Consider that valgrind isnt going to work on Win32) I also
> suspect that I forgot to send through a patch to win32/makefile.mk and
> win32/Makefile which were meant to accompany the doc patch. Im just
> resync'ing now so ill follow up on this later.
Actually theres nothing to follow up on. Steve fixed the issues that i
had in mind already. Thanks Steve.
And overall i would say that yes, the targets marked "not available"
probably never will be. Although thats just my $0.02.
Cheers,
Yves
--
First they ignore you, then they laugh at you, then they fight you,
then you win.
+Gandhi