| *|
++--+
Writing Makefile for Tornado::ConnectionHandler
Since PAUSE is down it hasn't been uploaded to CPAN yet. You can get it
here: http://keroes.com/perl/
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It's Tobacco time!
on.
> Maybe after that "is my bitch" business, I'm looking for slang from
> "the hood" everywhere.
Cuz ya know the Schwernmeister be keepin' it real here. Yo yo yo.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Obscenity is the last resort of the illiterate, Mother Fucker
-- KAL
.1
ok 2
ok 3
ok 4
4..1
Though now the 'no_plan' style in a subplan gets confusing. We might have
to change the no_plan style so that it has to produce some sort of header.
It might be literally "1..N".
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Cheating is often more efficient.
- Seven of Nine
On Thu, Aug 21, 2003 at 08:34:44AM -0500, Danny R. Faught wrote:
> Michael G Schwern wrote:
> >What books out there are of use for those wanting to learn Perl testing?
> >They don't necessarily have to be specificly about *Perl* testing.
> >I've put up a Wiki page
; *only* handles the single-process subplan, you'll
need to explain how "ok 1.2.3" isn't redundant.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
fused with the output of any other thread
> because every thing from thread 1 will have a number starting with 1. and
> thread 2 will have 2. etc
This is convincing.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Shrtr is btr.
-- Abhijit Menon-Sen in <[EMAIL PROTECTED]>
ant modules you're missing. I'm using
http://mungus.schwern.org/~schwern/cgi-bin/perl-qa-wiki.cgi?EssentialModules
for reference.
It looks like you've left off all CPAN modules which are also in the core,
I suppose you're figuring they'll be handled by the core smokers. Except
> How does it limit my implementation? Do you know for a fact that
> there are exactly 100 modules in the Phalanx 100? At one point, the
> count was 103, and that was fine by me. :-)
Fair nuff.
> >Here's some Really Important modules you're missing. I'm u
; 319.
> WHOA! Somehow you got a different number of results than tests ran!
> This should never happen! Please contact the author immediately!
> END failed--call queue aborted.
Looks like an ithreads bug. Forwarded it to p5p for analysis.
--
Michael G Schwern[EMAIL PROTECTED
ld be pretty trivial to rewrite your
system as a subclass of Test::Class and also to reimplement your assert
functions using Test::Builder.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Thanks, applied. Or, [EMAIL PROTECTED]
as we Bulgarian EBCDIC users like t
ave no idea, never having uses
> is_deeply().
is_deeply() should compare pretty much like is() which uses string equality.
So yes, is_deeply() should consider them equal.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Remember, any tool can be the right tool.
-- Red Green
*not* make it part of the public interface?
I'm betting not very often.
More importantly, I'm *not* betting against the test author. If they wrote
a test for string equality (which is what is() pretty much is) then that's
what they'll get.
--
Michael G Schwern[
sion."
> If you think the author, his very deliberately written code and 1
> reasonable interpretation of the documentation are all wrong then there is
> no point in continuing.
Well then, I guess there's no point in continuing. ;)
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Woah, like, did anybody see my watch?
iemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this special
biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
- End forwarded message -
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
Playstation? O
eading through
all the arguing, but don't let that hold you up Jarkko.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Cottleston, Cottleston, Cottleston Pie.
A fly can't bird, but a bird can fly.
Ask me a riddle and I reply:
"Cottleston, Cottleston, Cottleston Pie."
x them while introducing new ones on the assumption that folks
have worked around them and/or aren't bothered by them. I know folks are
bothered by the overload bug.
Sorry to be so troublesome about this, but as RFC 1925's Rule #1 states
"It Has To Work".
--
Michael
Work on
fixing them instead, please, then the real problem goes away.
http://www.pobox.com/~schwern/tmp/mcp_eol.wav
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Stupid am I? Stupid like a fox!
here possible,
however do not be tempted to use them to find out if something is
true or false!
# XXX BAD!
is( exists $brooklyn{tree}, 1, 'A tree grows in Brooklyn' );
This does not check if C is true, it checks if
it returns 1. Very different. Similar caveats exist for false an
On Sun, Oct 12, 2003 at 06:28:52PM +0200, Gabor Szabo wrote:
> That is, both test.pl and t/*.t were executed.
AFAIK its always been this way. DBI relies on it.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It should indeed be said that notwithstanding the f
ittle dubious anyway, there are POD-only modules.
> Some ideas:
> * wheater PREREQ_PM matches used modules (hard!)
Nearly impossible since:
require Foo::Bar if $some_condition;
Otherwise Module::Info->modules_used() can handle it.
--
Michael G Schwern [EMAIL PROTECTED] http://
s
run at "make test" time. DBI and the DBD::* modules use test.pl to display
benchmarking information.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
I know you get this a lot, but what's an unholy fairy like you doing in a
mosque like this?
e's nothing wrong with having sub-build directories.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Kindly do not attempt to cloud the issue with facts.
ake test". It just
> > runs and spits the output to the screen. If a test fails, "make test" will
> > still succeed. Still, its better than nothing at all.
>
> So t/* should hint more kwalitee than only test.pl
Yes.
--
Michael G Schwern[EM
On Wed, Oct 15, 2003 at 10:34:19PM -, Rafael Garcia-Suarez wrote:
> Michael G Schwern wrote in perl.qa :
> > This all suggests another check: stray files. Emacs backup files. CVS
> > directories. Empty directories. #...# backup files. Makefiles shipped
> > with M
ore because those modules
> rely on the features being tested. Most everything else can use
> Test::More. Barring any Unicode-related fiascos (of which I am proudly
> and blissfully unaware), they probably haven't been converted yet.
See perlhack for details.
--
Michael G Schwern
y upgrading Test::Harness. It should work back to 5.4.0.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
You and your "facts" and your "physics". Pah, I say.
http://www.goats.com/archive/981221.html
#x27;s buggy as hell. For example, in various versions
> of Perl I've used there have been rather serious bugs in the regex engine
> when taint mode is on, even when dealing with untainted variables!
I've never hit anything like this. Do you have examples?
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Loon.
ests and no dependencies.
Test-Simple's another good one. 44 programs, 267 tests, no dependencies,
backwards compatible to 5.4.0, does some complex stuff (evals, %SIG,
tied handles, system()...).
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Here's some scholarly-ass opinions...
On Tue, Oct 21, 2003 at 12:34:44PM -0500, Dave Rolsky wrote:
> Anyway, my taint mode experience has been that random things break in very
> weird ways when using it.
All the more reason to test with it on. :)
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
you've probably got a normal taint failure.
If it fails in any other way differently then a normal run you've got
a bug in taint.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
AY! The ground beef, she is burning my groin!
http://sluggy.com/d/990105.html
e skip_all will exit immediately you can fold that big "everything
inside the else block" away.
eval 'use Test::Pod';
my $have_testpod = !$@ and $Test::Pod::VERSION >= 0.95;
plan skip_all => "Test::Pod v0.95 required for testing POD"
unless $have_testpod;
my @file
On Sun, Oct 26, 2003 at 04:45:48PM +1100, Andrew Savige wrote:
> Michael G Schwern wrote:
> > Since skip_all will exit immediately you can fold that big "everything
> > inside the else block" away.
> >
> > eval 'use Test::Pod';
> > my $have_te
Test::Pod then you only have to depend on one module
instead pulling in the whole PodParser suite.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
We're talkin' to you, weaselnuts.
http://www.goats.com/archive/000831.html
smear mayonase on
your keyboard. :) For those special cases they can write special case
code to skip those files that should not be checked.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
The Power almighty rests in this Lone Ring.
The Power, alrighty, for doing
C or C without a sort.
Ummm... why?
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
list of guidelines of
> things to watch for. Lately, I've been spending my free time on prove
> and Test::Harness.
*cough*wiki*cough*
;)
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Stupid am I? Stupid like a fox!
d for the tests to run you might want to put that into a module
as well (look at MakeMaker::Test::Setup::* in a very recent MakeMaker for
an example).
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Playstation? Of course Perl runs on Playstation.
-- Jarkko Hietaniemi
On Sat, Nov 15, 2003 at 02:51:26PM +1100, Andrew Savige wrote:
> Michael G Schwern wrote:
> > I use t/lib so the top level t/ directory doesn't get cluttered (and for
> > compatibility with the Perl core which may be important later for A::T).
>
> Yes, I like that. S
rengthen them, the default should always be the
strongest testing position.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
"Congratulations, you're a thieving bastard... Now give me back my pants."
"That's MISTER Pants!"
-- Ian's Adventures In Morrowind
http://www.machall.com/morrowind/page3.html
ith the added functionality?
...you don't write wrappers around Test::More. You use the same underlying
class Test::More does: Test::Builder. This includes, oddly enough, like()!
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Do not try comedy at home! Mi
gt; Michael> name.
>
> As long as it's consistent, and I can set it easily in CPAN.pm without
> having to write a wrapper (via make_arg).
Consistency? I think you've chosen the wrong programming language, sir!
--
Michael G Schwern [EMAIL PROTECTED] http://www.p
> };
> like($ex, qr/Bad thing happened/, 'successfully tested bad thing');
>
>
> Now $ex is global but I think I cannot test within the catch block.
Why not?
catch MyError with {
like( $ex, qr/Bad thing/ );
};
--
Michael G Schwern[E
On Wed, Dec 03, 2003 at 10:20:03AM +, Fergal Daly wrote:
> On Tue, Dec 02, 2003 at 10:05:46PM -0800, Michael G Schwern wrote:
> > Why not?
> >
> > catch MyError with {
> > like( $ex, qr/Bad thing/ );
> > };
>
> If there is no exce
calibrated
relative to the current hardware. So a pmip on machine A would be
roughly twice as long as a pmip on a machine that's twice as fast.
This enables us to test "make sure this isn't too slow".
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
PS I am very handsome and I live in a castle with a pony.
gt; display benchmark info purely for informational purposes,
For that I'd recommend doing what DBI does and putting the benchmarking
code into test.pl.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Sometimes you eat the path, sometimes the path eats you.
conds, but it would be more accurate. C'est le testing.
> If Test::Harness had a protocol for warnings rather than just pass and fail
> then this would be more useful,
print STDERR or diag(). Test::Harness doesn't need to know anything about
warnings. If it can't fail
on fsck.com anywhere.
>
> Can someone tell me:
> (a) what I'm doing wrong
> (b) where to find information on these reports
> (c) whether there's a much more appropriate list for these questions
If you're feeling your oats you can hop onto irc.perl.org #perl an
0.00% 1-5
Five tests. Ten failures. Tests 1 through 5 failed. That might be a
problem.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
What about MY need to be generalized and easily dismissed?
http://www.goats.com/archive/000221.html
you'll need some way to
setup/teardown the tree between test runs to ensure its clean.
In that case a tarball or small perl script would be best.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
I've just gone through a lung-crushing breakup with my blender and I don't
think I should screw my forehead alone tonight.
ure".
Other Test modules don't have such well defined blocks, so I don't know
how well they'd fit in.
As for providing a Test::Builder default, for the time being just override
ok(). I don't think anything more than that is necessary at this point.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Please Captain, not in front of the Klingons.
ant" );
Or writing your own versions of isa/can_ok so that you, the programmer,
have full control over them.
I, the library designer, write isa_ok() and can_ok() as convenience
functions. Part of this convenience is providing sensible default names
so you don't have to.
--
Michael G S
{
$result = $TB->is_eq(@args);# everything else == is
}
$TB->diag($args[2]) if $args[2] and !$result;
return $result;
}
1;
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Please Captain, not in front of the Klingons.
xpected) ) {
$result = $TB->like($got, $expected);
}
else {
$result = $TB->is_eq($got, $expected);
}
$TB->diag($diag) if !$result and @_ == 3;
}
1;
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
3. With sufficient thrust, pigs fly
ts be captured as well.
Love to, but can't do it and still have T::H be cross-platform compatible. :(
What you can do is have your tests print your diagnostics as lines beginning
with a # to STDOUT. I believe T::H::Straps currently picks these up as
type "other" but it may chan
On Fri, Feb 06, 2004 at 03:14:33PM -0600, Scott Bolte wrote:
> On Fri, 6 Feb 2004 12:22:24 -0800, Michael G Schwern wrote:
> >
> > It wouldn't be Test::Harness, it would be a seperate Test::Depends or
> > something.
>
> I could live with that, but why do
so that other languages can
> write to the T::H format reliably, and let T::H become the uber-tester.
Some sort of BNF, if the syntax can be wedged into one, would be nice.
What does need to be done is for me to finish abstracting out the formatter
to allow custom harness more easily.
--
at if your
program walks outside its allocated memory space it immediately pukes.
However, I don't know how these will interact with Inline::C.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
That which stirs me, stirs everything.
-- Squonk Opera, "Spoon"
can call for help when I need
it.
[1] For those of you unfamiliar with Aegis, I wrote up a little
"Aegis From 10,000 Feet" piece a while back.
http://www.pobox.com/~schwern/tmp/aegis.nutshell
Just keep repeating to yourself, "Its not CVS. Its not CVS. Its not CVS."
--
Mic
most important thing to remember about a project like this is KISS.
Keep It Simple, Stupid. Features can rapidly spiral out of control, and
it'll never get done. But if we keep it simple something workable can
probably be knocked together in a few days.
I'm putting this up on the Make
er and it's mostly done. You just need a script to drive
> CPAN++ for testers to use to make things easier for them. Easy, simple,
> and effective if you can get people testing.
Turn around time too slow and requires a human.
--
Michael G Schwern[EMAIL PROTECTED] http://www
e you are going to have people
> forgetting to keep the central list up to date when then update their
> box.
This I don't understand. There's nothing for the user to keep up to date
by hand.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
HA HA HA You're all so rediculous! But thanks for the money!
t to
your inetd config.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Cuius rei demonstrationem mirabilem sane detexi hanc subscriptis
exiguitas non caperet.
On Thu, Feb 19, 2004 at 08:35:28AM +, Nick Ing-Simmons wrote:
> Michael G Schwern <[EMAIL PROTECTED]> writes:
> >One thing to keep in mind is portability. In order for this to be useful
> >it has to run on pretty much all platforms. Unix, Windows, VMS, etc...
> >
c/private key authentication I mentioned
earlier.
> Thing is who is going to give access to their machine(s) via some ad. hoc.
> scheme? I am not for a start.
Why would the method of network transport figure into that decision?
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobo
On Sun, Feb 22, 2004 at 06:36:22AM -0600, Scott Bolte wrote:
> On Sun, 22 Feb 2004 01:07:38 -0500, Michael G Schwern wrote:
> >
> > See above. Yes, ssh is not portable enough.
>
> Where is the gap? I have OpenSSH on every Unix platform I
> use and, wit
On Mon, Feb 23, 2004 at 08:04:14PM +0100, Thomas Klausner wrote:
> Is there any reason why BAIL_OUT is marked as unimplemented in the
> Test::More docs?
Because it is, in Test::More. I've yet to need it. Nobody's given me a
patch to implement it.
--
Michael G Schwern
per Perl
configuration.
> - since you talk about a central repository of public keys
This unnecessary complication has been eliminted. Individual authors looking
for testing machines are on their own for the time being.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
They just don't make any good porn music anymore, do they?
- WXDX DJ refering to "More, More, More"
sary logic to determine what
set of tests to run and feed that file list to runtests().
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It's Paint Chip Eating time!
my $num_left = $TB->expected_tests - $TB->current_test;
$TB->skip($why) for 1..$num_left;
exit;
}
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Let's leave my ass out of this, shall we?
skip and displays the reason.
use Test::More 'no_plan';
pass("Test this");
SKIP: { skip "because", 1 }
exit;
pass("This is never run");
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox
rep: we don't need no stinking database.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
ScHWeRnsChweRNsChWErN SchweRN SCHWErNSChwERnsCHwERN
sChWErn ScHWeRn schweRn sCHWErN schWeRnscHWeRN
SchWeRN scHWErn SchwE
tp://search.cpan.org/~mschwern/Test-Simple-0.47/lib/Test/More.pm#I'm_ok,_you're_not_ok.
That covers it, no?
I'll try to clear up the ambiguity around use_ok, require_ok and
is_deeply.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
You're smoother than a tunnel of shining sorrow.
is $__STDERR__, ''" is run. Simple enough since
$__STDERR__ is a tied variable.
That would seem to solve the problem.
Also, --no-trap-stdout and --no-trap-stderr options might be in order.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It's Flypaper Licking time!
#x27;s to shut it off:
=for testing
no_trap *STDOUT, *STDERR;
And turn it on.
=for testing
$__STDOUT__ = trap *STDOUT;
$__STDERR__ = trap *STDERR;
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
I'm exploring my nipples.
matically exits abnormally on failure but I'm considering
changing that to no longer be the default.
[2] Want some fun? http://search.cpan.org/~dconway
[3] Note to self: Write compatibility wrapper around Test::Builder to
emulate Test.pm so it can live together with Test::More.
--
Michael G S
n more easily do this sort of thing.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Cuius rei demonstrationem mirabilem sane detexi hanc subscriptis
exiguitas non caperet.
cal $^W = 0;
>
> -if( ! (ref $e1 xor ref $e2) and $e1 eq $e2 ) {
> +if( ! (ref $e1 xor ref $e2) and
> +! (defined $e1 xor defined $2) and
> +$e1 eq $e2 ) {
> $ok = 1;
> }
> else {
What version of Tes
Test::More and fail will no longer cause
'make test' to fail. But I doubt people are using test.pl and Test::More
much.
> > [2] Want some fun? http://search.cpan.org/~dconway
>
> You have a sick sense of humour young man ;)
He uses test.pl. Sic 'em.
--
Michael G
On Thu, Jul 08, 2004 at 08:59:38PM +0100, Fergal Daly wrote:
> On Thu, Jul 08, 2004 at 01:59:35PM -0400, Michael G Schwern wrote:
> > Likely you'd control if you wanted this behavior with
> > HARNESS_PERL_SWITCHES=-MTest::AutoDebug
> >
> > This can be implemen
use Test::Builder;
use Hook::LexWrap;
wrap 'Test::Builder::ok',
post => sub {
my $tb = shift;
my $ok = $_[-1];
enter_the_debugger if !$ok;
};
Or something like that.
--
Michael G Schwern[E
; (suites of suites etc) possible,
Yes, this is planned for 0.50. If nothing else it will let Test::Builder
test itself and make Mark Fowler handy.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Death was thought to be fatal.
-- Craig A. Berry in <[EMAIL PROTECTED]>
t the data being tested against, things going funny because the
environment changed, or an external utility (database).
Test coverage is a useful *heuristic* for test effectiveness. Like all
heuristics if you push it too far it falls apart. Get as close to 100% as
is useful and don't worry abo
$bar || 1;
$this || return;
Basically anything of the "$foo || constant" variety. Devel::Cover could
probably be smartened up to handle these cases better.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Fuck with me and I will saw off your legs.
http://www.unamerican.com/
On Fri, Jul 09, 2004 at 06:31:09PM -0400, Michael G Schwern wrote:
> Looking through a coverage analysis I just ran, here's some more idioms
> that trip up 100% coverage.
>
> my $foo = $bar || '';
>
> my $foo = $bar || 1;
>
> $this ||
pendency information. Simplest thing to do would be to make a
local miniCPAN mirror [1] and walk through the archive files [2] in
modules/02packages.details.txt looking for META.yml.
[1] http://www.stonehenge.com/merlyn/LinuxMag/col42.html
[2] Archive::Any will come in handy
--
Michael G Schwern
ment the
> tie hook routines.
I've just sent a patch to Richard to skip /^[A-Z]$/ by default. This nails
all the magic methods I can think of.
I just had an idea. Per module private/trustme lists for Pod::Coverage.
=for Pod::Coverage trustme
you_cant_find_my_docs()
=for Pod::Cov
http://mungus.schwern.org/~schwern/src/Test-Simple-0.48_02.tar.gz
A new alpha release of Test::Simple/More/Builder. You can consider this
the 0.49 release candidate. Please let me know how it goes.
There's a new feature. When run under Test::Harness diagnostic output will
throw in a le
both
> lots of SQL to a common format. Both seem much too cumbersome, however.
>
> Anyone have any brighter ideas?
Don't use a temporary database, just a temporary table.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Abandon failing tactics.
On Mon, Jul 19, 2004 at 10:19:47AM +0100, Tony Bowden wrote:
> On Mon, Jul 19, 2004 at 03:22:05AM -0400, Michael G Schwern wrote:
> > > The two "best" ideas we've had so far are to either run the SQL in the
> > > code against a temporary database, and then
t scripts, 0.00% okay. 1/4 subtests failed, 75.00% okay.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
The key, my friend, is hash browns.
http://www.goats.com/archive/980402.html
On Mon, Jul 19, 2004 at 04:25:35PM +0100, Adrian Howard wrote:
> On 19 Jul 2004, at 07:25, Michael G Schwern wrote:
> [snip]
> >There's a new feature. When run under Test::Harness diagnostic output
> >will
> >throw in a leading newline for better readability.
> [
ored CVS
repository, I might set that up, too.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
If at first you don't succeed, call in an air strike.
On Wed, 21 Jul 2004 14:51:13 -0400, Ricardo SIGNES
<[EMAIL PROTECTED]> wrote:
> I was going nuts recently, trying to figure out why I couldn't use
> is_deeply to compare objects. I've finally determined that it's only an
> issue (as far as I see) when comparing objects that overload
> dereferencin
On Thu, 29 Jul 2004 12:07:39 -0700, Geoffrey Young
<[EMAIL PROTECTED]> wrote:
> the Apache-Test integration stuff we talked about at YAPC works just fine
> with 0.48_02.
Lovely, thanks. As soon as I hear Test::Builder::Tester has adjusted
for the formatting change I'll release this as 0.49.
On Sun, 05 Sep 2004 19:38:12 -0400, Geoffrey Young
<[EMAIL PROTECTED]> wrote:
> just out of curiosity, what's the word on 0.49?
I've finally summoned the willpower to wrestle with Aegis to make
branch closing not be a gulag-like exercise. 0.49 is ready to go
except for some silly looking merge bu
Here's how it is as of 0.49.
If you want Test::More to be thread safe you have to "use threads"
yourself and do it before you use Test::More. This is a change from
previous versions. Previously I took the view that users will
probably get this wrong so I'll just do it for them. The change was
b
On Sun, 17 Oct 2004 01:12:45 + (UTC), Mark Stosberg
<[EMAIL PROTECTED]> wrote:
> It also worked. Here's what I used:
>
> `echo 'y' | my_shell_cmd`
>
> I'm sure there's some other cooler way, but this works well enough for me.
Eventually you'll want something more flexible and portable. You
Its about freakin' time. Has it really been two years since the last
stable release? Yes it has.
This is 0.48_02 plus a minor test and MANIFEST fix.
INCOMPATIBILITIES WITH PREVIOUS VERSIONS
* Threading is no longer automatically turned on. You must turn it on
before you use
Test::More if you
5.8 contains
a warning about the future reserved words. This follows the usual pattern
of breaking compatibility. Warn about it in one stable series then eliminate
it in the next.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
Home of da bomb
nt (read: compiled C code) goes.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
Life is like a sewer. What you get out of it depends on what you put into it.
- Tom Lehrer
601 - 700 of 1868 matches
Mail list logo
