All the Perl that's Practical to Extract and Report
use Perl Log In
Ovid (2709)
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
Order Restored
By the time you read this, merlyn will probably have passed me (again) as the number one monk on Perlmonks (discounting the site creator and his extra million XP, of course
In other news, we just hit 2000 tests for our latest project. Unfortunately, the tests were getting to be tough to manage as many of them took so long to run that it was tempting to skip the entire suite altogether (I suspect that some recent test failures were due to this problem). As a result, I wrote a little snippet to better manage tests. (the link is to a version that includes pod documentation)
#!/usr/bin/perl -w
use strict;
use Test::Harness;
use Getopt::Long;
BEGIN { chdir 't' if -d 't' }
my (@exclude,@include);
GetOptions(
'verbose!' => \$Test::Harness::verbose,
'quiet' => sub { $Test::Harness::verbose = 0 },
'include=s' => \@include,
'exclude=s' => \@exclude
);
@include = map { glob } @include;
@exclude = map { glob } @exclude;
my @files = @include;
unless (@files) {
@files = glob "*.t";
}
my @tests;
foreach my $file ( sort @files ) {
push @tests => $file unless grep { /\Q$file\E/ } @exclude;
}
runtests( @tests );
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Long-running tests (Score:1)
Neat script, by the way.
Re:Long-running tests (Score:2)
Glad you like the script. As for the perfomance problem, try running various combinations of this:
SELECT foo FROM bar WHERE baz LIKE '%quux%'And do that on huge tables. The LIKE clause negates the use of indices, so I'm not sure how to get around this problem. Unfortunately, due to business requirements, we have this repeatedly. If you have any suggestions ...
Re:Long-running tests (Score:1)
Re:Long-running tests (Score:1)
How about a test-only database, with just a few rows of data copied from the live database? The fewer rows to scan, the less time a search takes.
Re:Long-running tests (Score:1)
Re:Long-running tests (Score:1)
Run the customer/acceptance tests against a real database (but they get run once or twice a day rather than all the time so speed is less of an issue).
Test::Verbose (Score:2)
I do like the --exclude thing. Hopefully barrie can add something like that too.