http://www.pobox.com/~schwern/src/Test-Harness-2.25.tar.gz
Some bleadperl fixes for the tests under MacPerl were integrated, but in a
slightly different form than the original patches. They've been simplified
which eliminates the need for VMS specific code to fix the MacOS specific
code.
On Sun, Jun 16, 2002 at 12:14:59AM +0100, Adrian Howard wrote:
> 0) Do other people find this vaguely sane? Even possibly useful?
Yes! xUnit with a Perl spin is something I've wanted for a long time.
> 1) Is Test::Class the right name?
If you ignore the "it doesn't say it's xUnit" problem,
On Sun, Jun 16, 2002 at 03:12:17AM -0400, Michael G Schwern wrote:
> The Test::Harness::Straps part of 16938 has been defered until Pudge gets
> back to be with some more data. The patch only addresses the symptoms, the
> real problem is likely elsewhere.
> http:[EMAIL PROTECTED]/m
On Sun, Jun 16, 2002 at 08:28:26PM +0100, Adrian Howard wrote:
> >Now, the way I do this at the moment is have num_method_tests() walk up
> >the callstack until it finds a package that also isa Test::Class (in
> >this
> >case Base::Test) and then assume that is the class containing the method
> >
On Mon, Jul 01, 2002 at 09:57:24AM -0500, Andy Lester wrote:
> I can do this:
>
> use PHP::Session 0.10;
>
> to ensure a version number, but I can't do this:
>
> use_ok( 'PHP::Session', '0.10' );
>
> because I get this error:
>
> alester@flr4[~/tw/Dev]$ more Modules.t
> #!/usr/bin/per
On Sun, Jun 30, 2002 at 05:37:14PM -0700, chromatic wrote:
> Here's a patch to the Test::Simple 0.45 distribution to make isa_ok() work with
> class names, not just objects. It tries to respect custom isa() methods, as
> well.
The purpose of isa_ok() is two fold:
Check that a scalar contain
On Fri, Jun 28, 2002 at 02:34:48PM -0500, Danny Faught wrote:
> I just tried to install Test::More 0.45 under Cygwin on Windows 2000.
> It fails the output test. Same results on two different machines, and
> also on version 0.44. I'm running perl 5.6.1. All other tests pass.
> All tests, incl
On Thu, Jun 27, 2002 at 04:32:31PM +0200, Janek Schleicher wrote:
> I couldn't find a module doing this job on CPAN,
> so I'm ready to write a Test::Warn module.
>
> I thought that two methods should be implemented:
> warns_ok BLOCK REGEX, TEST_NAME (regex and test_name are optional)
> no_
On Sat, Jul 06, 2002 at 06:57:27PM -0700, chromatic wrote:
> My test was:
>
> use_ok( 'Child::Class' );
> isa_ok( 'Child::Class', 'Parent::Class' );
>
> I could just as easily check @Child::Class::ISA or use UNIVERSAL::isa().
Child::Class->isa('Parent::Class')
--
This sig file te
On Sat, Jul 27, 2002 at 09:44:03AM -0700, chromatic wrote:
> This patch captures messages sent through diag() and stores them in the
> diagnostic array. Now all of the information the tests generate is available
> for later inspection.
Dude, where's my patch?
--
Michael G. Sch
here's a slide in the
Test::Tutorial talk with a list current as of a month ago.
o If you don't already have them installed, you only need to do it once.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTE
Figured folks might be interested in slides from talks at OSCON:
http://www.pobox.com/~schwern/talks/How_To_Be_Lazy_Redux/
http://www.pobox.com/~schwern/talks/Test_Tutorial/
http://www.pobox.com/~schwern/talks/Writing_A_Test_Library/
--
Michael G. Schwern <[EMAIL PROTECTED]>
t, explaining how to do it, how perl5's tests are structured
> to reduce interdependencies, use Test::More; when Test::More is not
> appropriate.."
Porting/patching.pod
About the only thing that's missing is docs for t/test.pl.
--
Michael G. Schwern <[EMAIL PROTE
this is a request to place Inline::C into 5.9 to facilitate easy testing
of the C API.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
IMHO bugs in Perl 5 shouldn't carry over to
d.
+
+=back
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Tasty, yet morally ambiguous.
ilder, so
> REFCNT doesn't come to 0 before global cleanup.
Whoa, nice catch! And thanks for catching the missing t/has_plan's in the
MANIFEST. :)
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]>
is the best place to handle this.
Test::Harness 2.03 is a prerequsite of Test::More.
Either it didn't get installed for some reason or your old version is
shadowing. T::H somewhere around 1.2x installed itself into site_perl, not
the core, so you might have a leftover. Try a "make in
zabo via CPANPLUS. How about a way to _force_
> it to prompt or give up if that's really impossible?
A timeout argument to prompt() might be worthwhile. And an accompanying
environment variable.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
P
a prereq on
Test::Harness. The problem is the installation is almost always screwed up,
an old version of T::H winds up shadowing.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
It's Airplane Glue sniffing time!
http://www.pobox.com/~schwern/src/Test-Simple-0.47.tar.gz
Two major bugs were added in 0.46. Objects would accidentally be stored
internally causing destructors not to fire when people expected them to.
Also ithread support was broken. These have both been fixed.
0.47 Mon Aug 26 03:54:22
so it's not worth much.
What you should probably do is emit further diagnostic information on what
the test failure might mean like:
is($this, $that) || diag(<http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Monkey tennis
Then one could do something like this:
perl -Mblib=only t/foo.t
>Sorry if I've wasted your time by telling you something you
>already knew,
>or had inferred from Hugo's reply.
I might have inferred it, but this helped me understand various
implications, actually.
-Ke
sing a CPAN shell every module install is going to be a chore anyway.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
I blame myself. AND SATAN.
s are run. All non-XS modules
are never really "built", they're already in lib/. All XS modules are built
and their results put into lib/ and then the tests are run.
So, effectively, the core "installs" every modules into lib/ then runs all
their tests. This is so mo
lace that elsewhere things get more complicated
when trying to run an individual test:
./perl -It -MTestInit lib/Foo/whatever.t
or
./perl -I. -MTestInit ../lib/Foo/whatever.t
What it boils down to is how to you remove the need for the cargo-cult BEGIN
block in each test while still maki
hes back to the author.
Keeping them in sync with p5p's patches is the hardest part.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
There is a disurbing lack of PASTE ENEMA on the internet.
XS?
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Do you have a map? Because I keep getting lost in your armpits.
On Fri, Aug 30, 2002 at 11:57:16AM +0100, Nick Ing-Simmons wrote:
> Michael G Schwern <[EMAIL PROTECTED]> writes:
> >On Fri, Aug 30, 2002 at 05:54:15PM +1000, Ken Williams wrote:
> >> Oh, one big lib/, not several different ones? So then why can't it be
> >>
plit.ix
# Index created by AutoSplit for blib/lib/AutoExample.pm
#(file acts as timestamp)
package AutoExample;
sub foo ;
1;
$ perl -Mblib -wle 'use AutoExample; print "Yes" if AutoExample->can("foo")'
Using /home/schwern/tmp/AutoExample/blib
Yes
$ p
On Sat, Aug 31, 2002 at 02:05:53PM +0200, Elizabeth Mattijsen wrote:
> >$ perl -Mblib -wle 'use AutoExample; print "Yes" if
> >AutoExample->can("foo")'
> >Using /home/schwern/tmp/AutoExample/blib
> >Yes
>
> Hmmm... I'm doing B
rks just as well:
cd t; ./perl -I../lib foo/bar.t
Anyhow, t/TestInit.pm *already does this*.
schwern@blackrider:/usr/local/src/perl-current$ ./perl -It -MTestInit -wle 'print
@INC; use Cwd; print cwd;'
.../lib
/usr/local/src/perl-current/t
While the result is still ugly, it
Heck: with a smart enough TestInit, it could even adjust @ARGV
> so that you could specify all *.t paths in Unix format, if that
> would be helpful.
Hmmm. I can't think of a use.
> >and perhaps reduced a little further by moving/linking
> >TestInit.pm into the
> &g
an pages. It can produce HTML
and lots of other formats.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Still not king
s find lib/
> >>'.' won't necessarily be in the path anyway.
> >
> >Sorry, I ment perl's @INC.
>
> That's what I meant too. People can build Perl without '.' in
> @INC, right?
I don't think so.
--
Michael G. Schwern &
t variable Test::Harness responds
to.
Test::Class uses the TEST_VERBOSE environment variable to print out the name
of each test before it's run.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
It's Tobacco time!
est::More;
# Failed test (-e at line 1)
# Tried to use 'Test::More'.
# Error: You tried to plan twice! Second plan at (eval 1) line 3
# Looks like you failed 1 tests of 1.
schwern@blackrider:~/src/devel/Test-Simple$
I'll have to put in some special case code to make
oice was played by
Orson Wells in one of his last performances.
Anyhow, I know more about Unicron than Unicode.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Perl_croak(aTHX_ "Believe me, you don't want to use \"-u\" on a Macintosh");
-- toke.c
is a sign they like
> the overall picture. And my life is now better for realizing these two
> truths. :-)
We're Perl programmers. Praise is implicit, like everything else in the
language. :)
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl
ry::Heap;
my @array = (1..1);
HeapChange "creation of array";
my @dup = @array;
HeapChange "duplication of array";
A more broad Devel::Internals or a more user-friendly Devel::Memory can be
left for later, and the functionality of D
ler's namespace. So you can have
your methods which print neatly formatted diagnostics seperate from your
methods which simply return values.
> Used in scalar context returns the current sbrk value
Shouldn't sbrk() do that? Is this the same value as MemUsed() would pr
gt; >
> > ?
>
> See another answer in this thread proposing to return a list of lists. I like
> that.
Seperate out the three different pieces of functionality, returning the
current memory state, printing a memory diagnostic and returning the memory
history, into three differen
:Harness to be upgraded which has been
causing some problems lately. Something I'm moving to fix by making the
Test::Harness upgrade non-optional when you install Test::More. But that's
an implementation issue and will eventually fade away.
[1] This thinking makes me nervous, so I&#x
7;s threads just so I can remove a large volume
of work-around code.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
List context isn't dangerous. Misquoting Gibson is dangerous.
-- Ziggy
On Tue, Oct 15, 2002 at 10:34:26AM +0100, Nicholas Clark wrote:
> On Mon, Oct 14, 2002 at 09:00:42PM -0400, Michael G Schwern wrote:
> > 5.8.0's threads are giving me serious headaches. When 5.8.1 comes out I
> > might drop support for 5.8.0's threads just so I can rem
r an is_passing() method. Or both.
BTW How does one get the current srand if you use the one set by Perl?
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
I'm not actually Kevin Lenzo, but I play him on TV.
At YAPC::Europe there was some discussion about Test::Builder->level,
$Test::Builder::Level and the fact that they don't really work well as
implemented. I know we reached some sort of consensus about how to do it
better, but I've forgotten it.
Anyone remember?
--
Michael G. Schw
ecessary to load threads.pm
before Test::More or Test::Builder if you wish to use threads in your tests.
use threads;
use Test::More;
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]>
convinced its a good
idea.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Home of da bomb
http://www.pobox.com/~schwern/src/Test-Simple-0.48_01.tar.gz
Since there's a lot of internal and external change going on in this
release, I decided to put out an alpha first.
The external API changes:
* The Test::Harness upgrade is no longer optional.
* threads.pm is no longer automati
e object while leaving another in
a normal state to perform the tests.
The real reason why I put all the data into lexicals rather than a hash is
because its easier to type $Have_Plan than $self->{Have_Plan}.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schw
On Mon, Nov 11, 2002 at 02:51:00PM -0800, chromatic wrote:
> On Monday 11 November 2002 14:40, Michael G Schwern wrote:
>
> > > We *could* add a method called really_create_a_new_builder() that doesn't
> > > have the singleton properties, but what problem does that s
der::Level + 1;
>
> return $self->SUPER::like(@_)
>}
Oh, to have real end-of-scope conditions.
> > > > The real reason why I put all the data into lexicals rather than a hash is
> > > > because its easier to type $Have_Plan than $self->{Have_Plan}.
&g
;
> Or is this a sneaky way to get more people to install Test::More
> on their machines?
CPAN::MakeMaker?
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Ooops, fatal mutation in the test script.
sub real_test_func {
...
$TB->ok($test);
...
}
a practical example would be an Exporter/Exporter::Heavy poor-man's
autoloader setup.
Of course, there's nothing stopping you from overriding level() to be
magical, once I implement
- copies the state of one object to a new one
copy & share state- like copy, but test state is shared between the
original and the copy
with those plus the push/pop_stack methods you can pick and choose what sort
of state sharing you want.
--
Michael G. Schwe
r->create(state => $tb->state);
You're right, this one isn't necessary given the *state methods sketched out
above.
> >with those plus the push/pop_stack methods you can pick and choose what
> >sort
> >of state sharing you want.
>
> If we have explicit acce
Test::Foo::Inside;
sub wiffle {
something(@_);
}
...and in your test code...
use Test::Foo;
wiffle();
Ooops.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTE
use Test::More tests => 42;
use Test::Binary;
is(...);
binary_is(...);
See http://www.pobox.com/~schwern/talks/Writing_A_Test_Library/full_slides/
for details about using Test::Builder.
--
Michael G. Schwern <[EMAIL PROTECTED]&
After shuffling some files around and doing some permissions tricks, the
Perl QA Wiki is working again! Everything is now editable.
http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Ass
s to try and test in the script.
Beyond that the real problem is that scripts must be called as seperate
processes which makes much of the subroutine overriding tricks above
difficult. I have a trick which simulates running a perl script, but all
its really doing is eval'ing the code in th
On Mon, Mar 31, 2003 at 12:45:14PM +0100, Dominic Mitchell wrote:
> I've just uploaded a new module to CPAN[1], Test::XML. It contains a
> couple of functions for examining XML output of functions in a slightly
> saner way than is().
>
> http://search.cpan.org/author/SEMANTICO/Test-XML-0.03
On Thu, Jun 05, 2003 at 10:55:29AM +0100, Mark Fowler wrote:
> On Thu, 5 Jun 2003, [iso-8859-1] Andrew Savige wrote:
>
> > While a standard name is not required, having one would allow
> > automated CPAN test harnesses to run the longer tests.
>
> While we're on it, it'd be nice to have a standar
On Mon, Jun 23, 2003 at 05:49:06PM +0100, Fergal Daly wrote:
> I'm looking for comment or suggestions about this new module. It's
> independent of and complementary to Test::Warn. It tests that your test
> script didn't emit any warnings. Just add
>
> use Test::More::None;
>
> to the top
On Tue, Jun 24, 2003 at 10:59:43AM +0200, Tels wrote:
> > On Mon, Jun 23, 2003 at 05:49:06PM +0100, Fergal Daly wrote:
> >> I'm looking for comment or suggestions about this new module. It's
> >> independent of and complementary to Test::Warn. It tests that your test
> >> script didn't emit
On Tue, Jun 24, 2003 at 12:07:19PM +0100, Fergal Daly wrote:
> > Consider the following.
> >
> > use Test::More;
> > use Test::Warn::None;
> > plan tests => 42;
> >
> > To make this work I'd have to overhaul the internal Test::Builder planning
> > system to allow Test::Warn::None to s
On Tue, Jun 24, 2003 at 12:37:36PM +0100, Fergal Daly wrote:
> Also how about calling it Test::Warn::Auto? I'm not particularly happy with
> None,
Test::Warn::Auto doesn't say anything about its main purpose: to ensure
that you have no warnings. Instead it documents an implementation detail,
tha
On Tue, Jun 24, 2003 at 01:36:52PM +0200, Rafael Garcia-Suarez wrote:
> BTW, what about modules that define their own category of warnings
> (via warnings::register) ? It'd be useful to have a module to ease
> testing for warnings presence/absence on certain conditions.
There's Test::Warn, but I d
On Tue, Jun 24, 2003 at 02:04:25PM -0500, Andy Lester wrote:
> All this "make sure no warnings fired" is good thinking. But why not
> roll it into Test::Harness, and make it switch selectable? It's
> really T::H that we want keeping an eye on this, right?
No, its definately a test feature. Mu
On Wed, Jun 25, 2003 at 07:09:26PM +0100, Fergal Daly wrote:
> I just thought of a big problem with plan extensions. If the script silently
> eat's itself just before you extend the plan, then you don't know that
> anything went wrong.
It would have to also exit normally. That is rare.
--
Is
On Tue, Jun 24, 2003 at 08:39:39PM +0100, Fergal Daly wrote:
> Test::NoWarnings sounds good to me. What is the correct etiquette for
> abandoning a namespace? Just delete the files with PAUSE or should I leave a
> pointer behind? Not too important with this module but I'm just curious,
When I me
On Sat, Jun 28, 2003 at 10:13:06PM +0100, Fergal Daly wrote:
> On Saturday 28 June 2003 02:51, Michael G Schwern wrote:
> > When I merged Test::Simple with Test::More I left a Test-More tarball lying
> > around containing a Makefile.PL which simply died saying "download
>
On Sun, Jul 06, 2003 at 01:02:12PM +0100, Fergal Daly wrote:
> [EMAIL PROTECTED]:> perl Makefile.PL
> Writing Makefile for Test::Deep
> You tried to run a test without a plan! Gotta have a plan. at
> /usr/lib/perl5/5.8.0/Test/NoWarnings.pm line 99
> END failed--call queue aborted.
> # Looks like
Looking at the Perl bug overview yesterday, I noticed that we have 90-odd
open bugs which are listed as "notabug"! How odd.
Most of these are miscategoriezed. Some are just really old bugs that
have long since been fixed. Anyhow, its a big branch of low hanging fruit
to work on for closing perl
Having just had a really old notabug I sent a few years ago via an old
email address pointed out to me, I tried searching on bugs.perl.org for
"Requestor email address contains 'schwern'" and "Status isn't resolved".
Found seven, many about really old or deve
On Fri, Jul 18, 2003 at 12:00:55PM -0700, Robert Spier wrote:
> > There doesn't seem to be any documentation anywhere on this, and we
> > thought the QA wiki might be a useful place to try putting it
> > together.
>
> I'd rather something that can actually live on bugs.perl.org.
How about a bugs.
On Fri, Jul 18, 2003 at 06:36:41PM +0100, Tony Bowden wrote:
> What's the current approach to turning perlbugs into tests?
>
> Should they be done as TODOs? Is there a distinct set of test files for
> them? etc? Can they use Test::More? etc. etc. etc.
>
> e.g. http://bugs6.perl.org/rt2/Ticket/Di
On Fri, Jul 18, 2003 at 09:17:26PM -0700, Robert Spier wrote:
> > > I'd rather something that can actually live on bugs.perl.org.
> > How about a bugs.perl.org Kwiki?
>
> I have not yet drunk that particular Kool Aid.
I will unleash Ingy upon you when he gets back.
> I'm happy to accept patch
I have an odd proposition to make. I'd like to do some travelling in the
coming months. Specificly, I've a friend's wedding in Pittsburgh, PA I'd
like to attend in September and I'd really like to be there for the Global
Balalaika Show at the Helsinki Festival this year in August.
Of course, I'm
I had an idea yesterday. On more than one occassion, a I've been asked
about running tests against a live site. My usual waffle is to talk about
assertions or to build a seperate test suite which is explicitly non-modifying.
Or something Skud came up with which was to tag blocks of tests in the s
On Fri, Aug 01, 2003 at 01:07:15PM -0700, Michael G Schwern wrote:
> Another way is to use a TEST: block
> and have Filter::Simple strip them out.
>
> TEST: {
> cmp_ok( ... );
> }
> Questions? Comments? Approval?
Hell, why wait for wiser heads?
http://w
Make that...
http://www.pobox.com/~schwern/src/Test-AtRuntime-0.01.tar.gz
--
I knew right away that my pants and your inner child could be best friends.
On Sat, Aug 02, 2003 at 12:09:22AM +0100, Adrian Howard wrote:
> - Rather than running tests at live time, I'm more often doing the
> opposite. I have assertions that I only want to switch on at testing
> time since that is when I'm exercising things that might break.
>
> - This sort of
On Fri, Aug 01, 2003 at 11:02:19PM -, Rafael Garcia-Suarez wrote:
> Michael G Schwern wrote in perl.qa :
> > The only part missing is the ability to shut the tests off once you've
> > released it to production.
>
> You could perhaps use the assertion feature of per
http://www.pobox.com/~schwern/src/Test-AtRuntime-0.02.tar.gz
or a CPAN near you.
Still a few small bugs and missing features, but the important things work.
See the TODO and CAVEATS for details. Now works with 5.6.0!
NAME
Test::AtRuntime - Put tests in your code and run them as
On Sat, Aug 02, 2003 at 11:22:43AM -0700, chromatic wrote:
> Could these instead be subroutine attributes? I can see a lot of
> advantages there.
I know very little about subroutine attributes, so you're going to have
to investigate that one.
Keep in mind, though, that we want the *whole call t
On Sat, Aug 02, 2003 at 11:43:26AM -0700, Ovid wrote:
> This does mean, though, that it won't play nicely with versions of Perl < 5.6.0. Is
> that trade
> off acceptable?
I'll throw in the fallback "if DEBUG" style
TEST {
my $sky = look('up');
is( $sky, 'blue' );
} if
On Sat, Aug 02, 2003 at 05:02:58PM +0100, Adrian Howard wrote:
> >Or even more trivially, take Test::AtRuntime and swap
> >out Test::Builder::ok() with something that dies on failure.
> [snip]
>
> I was thinking about the ability to have an assertion block - so you
> could do (something like):
>
As I've obtained a stable server on which I have root, I've moved the
QA Wiki there so the permissions problems which have plagued it will be
no more!
The existing URL will work fine.
http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi
--
Michael G Schwern[EMAIL PROTEC
about *Perl* testing.
I've put up a Wiki page to generate a listing.
http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi?TestingBooks
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Death was thought to be fatal.
-- Craig A. Berry in <[EMAIL PROTECTED]>
On Fri, Aug 15, 2003 at 09:25:05AM -, Rafael Garcia-Suarez wrote:
> Michael G Schwern wrote in perl.qa :
> > http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi
>
> Do you want a link to this from qa.perl.org ?
Sure.
--
Michael G Schwern[EMAIL PROTECTED] http:
ard test for valid "portable" path names.
> Does such a test exist? I noticed Archive::Any has is_impolite() and
> is_naughty() but didn't see any checks for basic path name validity.
> BTW, is Archive::Any a "dead camel"?
Its just resting.
--
Michael G Schwern
the net effect of the individual changes.
Says who?
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It's Airplane Glue sniffing time!
f
the screen to distinguish it from the code when you use POD. Might I
suggest a good syntax highlighting editor?
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
The key, my friend, is hash browns.
http://www.goats.com/archive/980402.html
perl-mode will do it.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Hey Schwern! honk, honk, honk, honk, honk, honk, honk, honk,
honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk,
honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk,
h
On Thu, Jul 24, 2003 at 10:55:57AM +1000, Andrew Savige wrote:
> I'd be interested to see an example of sub-classing Test::Harness.
See examples/mini_harness.plx in Test::Harness.
The straps interface is not yet entirely usable.
--
Michael G Schwern[EMAIL PROTECTE
nning with whitespace. If a test fails inside a sub block, the error will
> propogate all the way to the outermost block so TH will see it. So you can
> test this out without modifying TH, although it would be nice if TH
> understood this format.
I don't think we can
On Wed, Aug 20, 2003 at 10:34:08AM +0100, Fergal Daly wrote:
> On Wednesday 20 August 2003 08:23, Michael G Schwern wrote:
> > You don't want subtests to have to know any state, such as how far to
> > indent. Why? Consider:
>
> Something has to keep state
The stat
raft animal so that it can be attached to and
pull a cart
Test::Harness::Parser would have been a better name, but hey, you're
talking to the author of Ima::DBI.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Global communism.
On Wed, Aug 20, 2003 at 02:00:28PM +0100, Adrian Howard wrote:
> On Wednesday, August 20, 2003, at 11:52 am, Michael G Schwern wrote:
> [snip]
> >I've yet to see a real use-case for plans of plans.
> [snip]
>
> Anywhere when you want to have plans at a higher level of
uot;);
local $ENV{FOO} = '';
system("%^X foo.t");
{ local $ENV{FOO};
delete $ENV{FOO};
system("$^X foo.t");
}
A cheap way to run a single test in a variety of different environments.
Or...
foreach my $test (glob("t/subdir/*.t"))
501 - 600 of 1868 matches
Mail list logo
