Re: a less fragile way to test when we need to read and write to STDOUT?

On Fri, Apr 01, 2005 at 03:17:38AM +, Mark Stosberg wrote: > > sub echo { > > my($input, $command) = @_; > > > > local(*READ, *WRITE); > > open2(*READ, *WRITE, "$DARCS $command"; > > print WRITE "a\n"; > > Thanks for the tip. On this line, did you mean to write > >

Re: Why a scoreboard?

On Fri, Apr 01, 2005 at 03:30:44PM -0600, Andy Lester wrote: > Why is there a scoreboard? Why do we care about rankings? Why is it > necessary to compare one measure to another? What purpose is being > served? I presume you mean the CPAN scoreboard? Or maybe the Kwalitee scoreboard, it doesn't

Re: Why a scoreboard?

On Sat, Apr 02, 2005 at 01:43:47AM -0600, Andy Lester wrote: > I'd be far more interested with we can tell about modules on their own > and how they can be improved, rather than make it a competition. Maybe then it should track modules rather than authors. The top AND the bottom along with a qui

Re: Why a scoreboard?

On Sat, Apr 02, 2005 at 11:29:17AM +, Smylers wrote: > Indeed, and those also have odd effects: rather than being pure measures > of users' abilities/reputations/whatever, their very existence changes > how some users behave, where they do things specifically to increase XP > rather than becaus

Re: Kwalitee and has_test_*

On Sun, Apr 03, 2005 at 03:09:17PM -0700, Yitzchak Scott-Thoennes wrote: > Since you ask... > > An important part of kwalitee to me is that Makefile.PL / Build.PL run > successfully with stdin redirected to /dev/null (that is, that any > user interaction be optional). > > Another is that a bug-r

Re: TestSimple/More/Builder in JavaScript

On Thu, Apr 07, 2005 at 11:23:59AM -0700, David Wheeler wrote: > Greetings fellow Perlers, > > I'm pleased to announce the first alpha release of my port of > TestSimple/More/Builder to JavaScript. You can download it from: > > http://www.justatheory.com/downloads/TestBuilder-0.01.tar.gz Zee

Re: How to force tests to issue "NA" reports?

On Thu, Apr 07, 2005 at 05:01:34PM -0500, Ken Williams wrote: > >Is there a way tests to determine that a module cannot be installed on > >a platform so that CPANPLUS or CPAN::YACSmoke can issue an "NA" (Not > >Applicable) report? AFAIK NA reports are issued when a Makefile.PL dies due to a "req

Re: TestSimple/More/Builder in JavaScript

On Thu, Apr 07, 2005 at 04:17:03PM -0700, David Wheeler wrote: > Well, right now, isDeeply() should do the right thing. I could just > comment out the eqArray() and eqAssoc() functions, or make them tests, > too. That'd be pretty easy to do, actually. If you have isDeeply() there's little point

Re: TestSimple/More/Builder in JavaScript

On Fri, Apr 08, 2005 at 12:36:16PM -0400, Geoffrey Young wrote: > as someone familiar with T::M and not javascript, were I to try to use this > it's an additional barrier to call it "Test::More in JavaScript" but not > provide _the exact same functions_ as Test::More. now before everyone > starts

Re: How to force tests to issue "NA" reports?

On Thu, Apr 07, 2005 at 07:49:40AM -0500, Chris Dolan wrote: > >Is there a way tests to determine that a module cannot be installed on > >a platform so that CPANPLUS or CPAN::YACSmoke can issue an "NA" (Not > >Applicable) report? The only way I know of to do this currently is for Makefile.PL to

Re: Difining an array

On Mon, Apr 11, 2005 at 10:12:56AM -0500, Andy Lester wrote: > On Mon, Apr 11, 2005 at 11:43:34AM -0300, LOGGOS TI ([EMAIL PROTECTED]) wrote: > > my @{$Tempo}; > > This should never have worked. I'm surprised it ran in 5.6. It's not > legal. > > Regardless, this mailing list isn't the place for

Re: Testing for NULL return values in test scripts

On Tue, Apr 12, 2005 at 01:39:59PM -0500, Walter Goulet wrote: > I can't use Test::Simple, I have to use Test.pm for this module for > backwards compatibility reasons. Try Test::Legacy, it gives you an upgrade path away from Test.pm. http://search.cpan.org/dist/Test-Legacy/ It almost perfectly em

Re: Testing for NULL return values in test scripts

On Tue, Apr 12, 2005 at 10:57:02PM +0200, Tels wrote: > > Try Test::Legacy, it gives you an upgrade path away from Test.pm. > > http://search.cpan.org/dist/Test-Legacy/ > > > > It almost perfectly emulates the Test.pm interface and it works in > > conjunction with other test modules. If you're wor

Re: Testing for NULL return values in test scripts

On Tue, Apr 12, 2005 at 04:15:01PM -0500, Walter Goulet wrote: > I think the suggestion to use Test::Legacy was based on the statement > 'backwards compatibility reasons' require me to use Test.pm. I should > have been clearer in my explanation; the module author is not > permitting me to use any a

Re: Testing Ties

On Tue, Apr 12, 2005 at 06:58:34PM -0400, James E Keenan wrote: > How do you test that a variable has been tied to a class? $ perldoc -f tied tied VARIABLE Returns a reference to the object underlying VARIABLE (the same value that was originally returned by the

Re: Test automation with perl.

On Wed, Apr 13, 2005 at 02:45:53PM +0100, Adrian Howard wrote: > Darcs has some of its tests written in > Perl. PS If you're going to look at darcs' test suite look at darcs-unstable, not the latest release. Its test suite is in much better shape.

Re: Testing for NULL return values in test scripts

On Wed, Apr 13, 2005 at 03:52:43PM -0500, Walter Goulet wrote: > So the good news is that I was able to convince the author to let me > include my dependancies in the test library. So I'll switch to > Test::More. Huzzah for sanity!

Re: TestSimple/More/Builder in JavaScript

On Sun, Apr 17, 2005 at 05:23:56PM -0400, jesse wrote: > I'm betting there is no javascript community organization we can > leverage. Perhaps the DynAPI folks might be interested. http://dynapi.sourceforge.net/dynapi/ And then there's the whole Ajax thing which I'm not really up on enough to dete

Re: TestSimple/More/Builder in JavaScript

On Sun, Apr 17, 2005 at 04:26:32PM -0700, David Wheeler wrote: > On Apr 17, 2005, at 3:12 PM, Michael G Schwern wrote: > >Perhaps the DynAPI folks might be interested. > >http://dynapi.sourceforge.net/dynapi/ > > Perhaps, But then the mail lists are simply hosted by SourceFo

Re: Module and package version numbering

On Mon, Apr 18, 2005 at 05:03:42PM +0100, David Cantrell wrote: > 1) Am I correct to seperate the package version (1.3004) from the > versions of the several modules contained therein - and if not, where > should the package version number come from? and There is no correct here. As long as eac

Re: Module and package version numbering

On Mon, Apr 18, 2005 at 02:00:23PM -0700, David Wheeler wrote: > On Apr 18, 2005, at 12:50 PM, Adrian Howard wrote: > >Personally I prefer separate version numbers per-module, but some > >people don't. I've yet to read anything /really/ convincing for either > >side - so I'd do whatever you're

Re: [Module::Build] Re: Test::META

On Wed, Mar 30, 2005 at 05:53:37PM -0500, Randy W. Sims wrote: > Should we completely open this up so that requires/recommends/conflicts > can be applied to any action? > > install_recommends => ... > testcover_requires => ... > etc. This sounds useful and solves a lot of problems at one sweep.

Re: is_deeply hangs

On Sun, Jan 23, 2005 at 08:22:37PM +, Fergal Daly wrote: > Attached is a patch that fixes this test case without breaking any others so > I think it's OK. It basically centralises the circular ref checking into > _deep_check and then reroutes eq_array and eq_hash into that. This ensures > that

Test::Tutorial needs updated

And I just can't seem to get up the enthusiasm to do it. The primary problem is its testing against a very old version of Date::ICal and a lot of the examples no longer work. There's lots of secondary problems resulting from it having been written almost four years ago. So if anyone's feeling

[ANNOUNCE] Test::Simple/More/Builder 0.59_01

http://www.pobox.com/~schwern/src/Test-Simple-0.59_01.tar.gz or http://svn.schwern.org/svn/CPAN/Test-Simple/trunk or a CPAN near you Why an alpha release? The internal structure of the Test::Builder object has changed from a pile of file scoped lexicals to an actual object. The change was rote bu

Re: Overriding Test::Builder::ok

On Mon, Jan 24, 2005 at 12:56:22PM -0800, Ovid wrote: > Well, OK. So I tried it: > > use Test::More qw/no_plan/; > use Test::Builder; > use Hook::LexWrap; > use Data::Dumper; > > wrap Test::Builder::ok ^ ^ comma mi

Re: verbose diagnostics

On Thu, Apr 28, 2005 at 02:44:30PM +0100, Adrian Howard wrote: > > On 28 Apr 2005, at 14:23, Paul Johnson wrote: > > >Using Test::More, I would like to send some diagnostics to be seen only > >when the harness is running in verbose mode. > [snip] > > diag "some verbose diagnostics" if $ENV

Re: verbose diagnostics

On Thu, Apr 28, 2005 at 10:08:00PM -0400, James E Keenan wrote: > Fergal Daly wrote: > >Where is TEST_VERBOSE documented? I see HARNESS_VERBOSE in > > > >http://search.cpan.org/~petdance/Test-Harness-2.48/lib/Test/Harness.pm > > http://search.cpan.org/grep?release=Test-Harness-2.48&string=TEST_VER

[ANNOUNCE] Test::Simple/More/Builder 0.60

users of older versions of the dor patch before err() was weakend. [rt.cpan.org 8734] -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern 'All anyone gets in a mirror is themselves,' she said. 'But what you gets in a good gumbo is everything.'

Displaying the description in diagnostic output

see" # (/Users/schwern/tmp/during.t at line 6) # got: '42' # expected: '23' I'm pretty happy with that but I'd like feedback. I've attached the patch so folks can play around with it. Let me know what you think. -- Michael G

Re: Displaying the description in diagnostic output

> Should there be a way to turn on/off the description? A higher verbosity > level? I can't think of a reason for it, but... YAGNI. FWIW the description is only shown when running in a harness because otherwise you can see it in the "ok" line. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL! EVERYONE DIES! http://www.somethingpositive.net/sp05032002.shtml

Re: DBD-mysql coverage == 56% - am I on drugs ??

ly the tests just aren't that great. The good news from your perspective is you can do a lot of good with a little effort. Hop to it, hopilte! :) -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Just call me 'Moron Sugar'. http://www.somethingpositive.net/sp05182002.shtml

Re: DBD-mysql coverage == 56% - am I on drugs ??

most undertested? As for why no 100% coverage... test cases are often written in response to bugs and not in an attempt to cover all functionality. You can debate the merits of either approach, but that's the way some folks do it. -- Michael G Schwern [EMAIL PROTECTED] http://

Re: [Maybe Spam] Re: DBD-mysql coverage == 56% - am I on drugs ??

refer to popularlity. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern 'All anyone gets in a mirror is themselves,' she said. 'But what you gets in a good gumbo is everything.' -- "Witches Abroad" by Terry Prachett

Re: Displaying the description in diagnostic output

n unnecessary inconsistency. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL! EVERYONE DIES! http://www.somethingpositive.net/sp05032002.shtml

Re: Testing approach for server programs

start it and leave it running. Set it to shutdown after N minutes of inactivity. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick

Re: turning Test::More on or off at runtime?

()d... I suspect you're doing this: use Test::More tests => 7; and you want this: use Test::More; if( $Run_Tests ) { plan tests => 7; } -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that w

Re: Displaying the description in diagnostic output

different wordings of the same diagnostic message. Now that's confusing. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL! EVERYONE DIES! http://www.somethingpositive.net/sp05032002.shtml

Re: Test::Object

> of specific ones for the parents. Sounds like Test::Class. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!

Re: Module::Build::TestReporter 1.00 Preview

expected: 'bar' > # ' Test::More 0.48_02 introduced a change where it would put a leading newline before its diagnostics when running under Test::Harness. Looks like the test expected that. You're probably running Test::More 0.47. -- Michael G Schwern [EMAIL PROT

Re: Phalanx 100 list

ut next to each module. There are some head scratchers in there, like Class::WhiteHole, unless you realize its part of a dependency chain. It seems like the reasoning can be broken down into "important module", "dependency of an important module" or "widely used dependency&quo

Re: Extraneous whitespace on failures with T::Harness 0.48, T::More 0.60

tests of 2. It determines its running under Test::Harness by looking at the HARNESS_ACTIVE environment variable. Unfortunately Test::Harness sets this variable at load time rather than only when running tests which is why you get the newline even if Test::Harness is merely loaded. --

Re: prove with Devel::Cover example?

On Fri, Jun 03, 2005 at 02:04:50PM -0500, Pete Krawczyk wrote: > }How can I use 'prove' and Devel::Cover together? I tried: > > HARNESS_PERL_SWITCHES=-MDevel::Cover prove file.t Kinda surprised there's not a --cover switch. -- Michael G Schwern [EMAIL PROTECTED]

is_deeply() and code refs

ide, for the moment). Given that is_deeply() considers these to be equivalent: is_deeply [ 42 ], [ 42 ]; I think comparing the decompiled source code is consistent, but is it useful? Anyone have use cases for this? -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwe

Re: is_deeply() and code refs

ow a spanner into the works. Storable uses B::Deparse when > serialising coderefs, though, so I'm certain there's a way around > this. That shouldn't matter because any oddities B::Deparse applies to one code ref it will apply to the other. For equivalent code the decompi

Re: is_deeply() and code refs

; Just for clarification: this means that: > > is_deeply( sub { 1 + 2; }, sub { 3; } ); > > should/will pass because the subs compile to the same code? Yes, it will pass. "Should" is a matter for, largely academic, debate. -- Michael G Schwern [EMAIL PROTECTED]

Re: is_deeply() and code refs

On Sun, Jun 26, 2005 at 01:18:42AM -0400, Collin Winter wrote: > With this matter sorted, I've started on the code > and requisite tests to make the new stuff work. Ok, let me know when you have something. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern

Re: is_deeply() and code refs

dent for code ref testing we have, Test.pm, behaves and it is not to be followed. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick

Re: is_deeply() and code refs

gt; might be better to just get access to the original string of code > before it gets compiled, If they want to compare the original string they should have put it in their data structure. Simp. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern 'All anyone get

Test::More diagnostic change... again

/test at line 5 # got: '42' # expected: '23' There was some debate about the details, I don't remember how it all turned out but I like this new format. Any objections before I chuck it in? -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/

Re: is_deeply() and code refs

; case is to apply it to other references. is_deeply( eval "{ foo => 42, bar => 23 }", { "bar", 42, "foo", 23 } ); Even though the code is written differently the resulting data is the same. Would anyone be in doubt that it should pa

Re: Re: is_deeply() and code refs

s. is_deeply( eval "{ foo => 42, bar => 23 }", { "foo", 42, "bar", 23 } ); That's what I meant. Its much the same way that this is expected to pass: is( 1 + 1, 2 ); -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern 'All anyone gets in a mirror is themselves,' she said. 'But what you gets in a good gumbo is everything.' -- "Witches Abroad" by Terry Prachett

Re: Fwd: [CPAN Upload: P/PE/PETDANCE/Test-Harness-2.51_02.tar.gz: [EMAIL PROTECTED]

s got confused. Maybe it could key on an environment variable? -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL! EVERYONE DIES! http://www.somethingpositive.net/sp05032002.shtml

Re: Test::More diagnostic change... again

On Mon, Jun 27, 2005 at 11:08:40AM +0200, David Landgren wrote: > I ranted a while back about s/got/received/ Yeah, that's a different issue. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn&#

Re: is_deeply() and code refs

, they could use XS to create subref_eq which > pokes around inside closures, comparing the code and also comparing > the value of closed variables but that seems extreme, At that point you might as well just fix B::Deparse. -- Michael G Schwern [EMAIL PROTECTED] http://www.p

Re: is_deeply() and code refs

e your test died before it could output anything. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Don't try the paranormal until you know what's normal. -- "Lords and Ladies" by Terry Prachett

Re: is_deeply() and code refs

. It was undefined, accidental behavior. If anyone was relying on it I haven't heard. I didn't even notice code refs were broken until Collin brought it up and I'm not sure exactly when they broke. Yes, its in bleadperl. -- Michael G Schwern [EMAIL PROTECTED] http://ww

Re: Test::User, Test::Symlink

he proper uid and gid is? Can't it figure it out from the name? In fact, wouldn't that be more robust since the uid/gid on the system might change but the name will stay the same. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern 'All anyone gets in a mirror is themselves,' she said. 'But what you gets in a good gumbo is everything.' -- "Witches Abroad" by Terry Prachett

Re: Test::User, Test::Symlink

am('nik') ); are equivalent. But I realize now this is not a good idea because it leaves the user unable to express "I don't care what the UID is". > Any concerns about the namespace? I thought perhaps > >Test::Unix::User >Test::Unix::Gr

Re: Question about Test::WWW::Mechanize

the documentation isn't explicit about it. Test::WWW::Mechanize apparently expects something else to set up the plan. In all the tests it uses Test::More to do this. use Test::More tests => 5; use Test::WWW::Mechanize; ...test as in the docs... The docs

Re: is_deeply() and code refs

of internal difference but is there a detectable difference at the Perl level? -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!

Fwd: [demerphq@gmail.com: Re: fixing is_deeply]

Yves has some controversial ideas about what is and is not data structure equivalence. I'd like comments on it. - Forwarded message from demerphq <[EMAIL PROTECTED]> - From: demerphq <[EMAIL PROTECTED]> Date: Thu, 30 Jun 2005 23:17:19 +0200 To: Michael G Schwern

Re: Fwd: [demerphq@gmail.com: Re: fixing is_deeply]

ays run an addition test. But if we made is_deeply() repeating reference aware then the user who does not care about that cannot use is_deeply() at all. So, I conclude that is_deeply()'s behavior is ok and something like Test::Deep should be enhanced with an option to deal with this problem. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Just call me 'Moron Sugar'. http://www.somethingpositive.net/sp05182002.shtml

Re: is_deeply() and code refs

that the output from coderef2text() cannot be eval'd into a routine with the same functionality. It causes problems in serialization. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!

Re: Fwd: [demerphq@gmail.com: Re: fixing is_deeply]

is_deeply() is not about exact equivalence. Its about making a best fit function for the most common uses. I think most people expect [$a, $a] and [$b,$c] to come out equal. Test::Deep is for tweaked deep comparisons. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/

Re: Fwd: [EMAIL PROTECTED]: Re: fixing is_deeply]

else has been surprised by this sort of behavior before, please say so. Additionally I'm queasy about how much code this change will break. Ovid suggested making the change and running it against a large corpus of existing tests, such as the Perl core. I'd like to see that done as it would

Re: [EMAIL PROTECTED]: Re: fixing is_deeply]

to look for conversations. Contrast this to email and mailing lists where I control my MTA interface and its "push" so everything comes to me, I don't have to go chasing it. If it was mirrored as a mailing list that would increase the probability I might pay attention to Perlmonks (

Re: Fwd: [EMAIL PROTECTED]: Re: fixing is_deeply]

two positions cannot co-exist in the same function. One is not right nor wrong, they're just different functions. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Just call me 'Moron Sugar'. http://www.somethingpositive.net/sp05182002.shtml

Re: [EMAIL PROTECTED]: Re: fixing is_deeply]

On Fri, Jul 01, 2005 at 02:39:46PM +0200, demerphq wrote: > On 6/30/05, Michael G Schwern <[EMAIL PROTECTED]> wrote: > > Yves has some controversial ideas about what is and is not data structure > > equivalence. I'd like comments on it. > > Well while im disappoi

Re: is_deeply and overloading

point where values are unoverloaded. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL! EVERYONE DIES! http://www.somethingpositive.net/sp05032002.shtml

Diagnostics changed to include test description

suspect this will affect your module pull the latest version off svn.schwern.org and give it a whack. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick

like, cmp_ok and undef

mething like: like( $foo, qr/.../ ); and: cmp_ok( $foo, 'eq', $bar ); warning about $foo being undefined? Especially since the test diagnostics will let you know about what was undef. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Don't t

Re: Fwd: [EMAIL PROTECTED]: Re: fixing is_deeply]

a lie. No, we just differ on what "different" means. However, I do admit the docs are not exactly thorough. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern You are wicked and wrong to have broken inside and peeked at the implementation and then relied upon it. -- tchrist in <[EMAIL PROTECTED]>

Re: Fwd: [EMAIL PROTECTED]: Re: fixing is_deeply]

g each data structure to see if they > are equivalent. If the two structures are different, it will display > the place where they start differing." No argument there, is_deeply() is underdocumented. (That's your cue to provide a patch.) -- Michael G Schwern [EMAIL PROTECTE

Re: like, cmp_ok and undef

ntention of the tester. If they craft a match which matches against undef then the test passes. But a warning serves its purpose of "hey, are you SURE you wanted this?" and they can choose to supress it. Now all I have to do is figure a clever way to supress all but uninit warnings w

Re: Fwd: [EMAIL PROTECTED]: Re: fixing is_deeply]

On Sat, Jul 02, 2005 at 09:50:24AM -0700, Andrew Pimlott wrote: > Finally, I think that comparing functions (which started this > discussion) is insane! You haven't done much testing of serialization. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Real

Re: Fwd: [EMAIL PROTECTED]: Re: fixing is_deeply]

eful :) Seconded! Go code something. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!

Re: Feedback from a first time Test module author.

return unless $Show_Diag; > since $Show_Diag is private it means you have to use Test::More's diag > routine to play nicely with its behaviour. I guess an option would be > to put this behaviour in Test::Builder's plan method or something. > (the 'no_diag'

Re: Feedback from a first time Test module author.

override Test::More's functions, or any other module's, but they're not worth elaborating on as 99.99% of the time its the wrong thing to do. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern You are wicked and wrong to have broken inside a

Re: Fwd: [EMAIL PROTECTED]: Re: fixing is_deeply]

On Sun, Jul 03, 2005 at 01:53:45PM +0200, demerphq wrote: > Actually about the only thing that seems to be really "hard" is doing > comparison of blessed regexes with overloaded stringification. For > that you need XS if you want it to work always. Ow my BRAIN! -- Michael G

Re: Feedback from a first time Test module author.

On Sun, Jul 03, 2005 at 04:16:25PM +0200, demerphq wrote: > On 7/3/05, Michael G Schwern <[EMAIL PROTECTED]> wrote: > > What framework is this? Oh, you mean Test::Simple::Catch? Its not really > > suitable for release. In fact the way I test Test::More is far inferior to

Re: Feedback from a first time Test module author.

d like TB you'd make a TB subclass, put your methods in that and then have a separate module which uses (delegates to) your TB subclass for a grand total of two custom classes. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Don't try the paranormal until you know what's normal. -- "Lords and Ladies" by Terry Prachett

Re: Putting a standardized import() into Test::Builder (was Re: Feedback from a first time Test module author.)

e for the external behaviors of the module, such as exporting. You'll probably not inherit from it but rather it would export its functions, effectively a mixin, but I'm not sure right now. I guess I need to think about what it would do beyond exporting. -- Michael G Schwern [EMAI

5.004_xx in the wild?

they were actually developing on a newer perl? -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick

[ANNOUNCE] Test::Simple/More/Builder 0.60_01

an.org 8865] - Files opened by the output methods are now autoflushed. - todo() now honors $Level when looking for $TODO. 0.54 Wed Dec 15 04:18:43 EST 2004 * $how_many is optional for skip() and todo_skip(). Thanks to Devel::Cover for pointing this out. - Removed a user

Re: 5.004_xx in the wild?

y my regexes are small. Other than that there's just the wild assortment of minor bugs to deal with. Fortunately now that I have a working 5.4.5 on my OS X laptop I can seriously test against it again. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL!

Re: 5.004_xx in the wild?

(whether warrented or not) than furthering development. I just had exactly this happen to a friend of mine contracting at a company still running 5.5.3. He couldn't even convince them to install a modern Perl in a separate location and leave the old code running 5.5.3. -- Michael G Schwern

Re: 5.004_xx in the wild?

h the initial pain of backporting its not too big a deal to keep things working as long as you're not doing XS. qr// is the only thing I really miss. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL! EVERYONE DIES! http://www.somethingpositive.net/sp05032002.shtml

Re: 5.004_xx in the wild?

ild.PL (they can distribute a copy with their module as things like Test::More are done) at least they don't have to reinvent the wheel. But then stats are selected by individual author who wishes to have their mod phone home. Sucks either way. -- Michael G Schwern [EMAIL PROTECTED]

Re: 5.004_xx in the wild?

t; bugger to work around. Trivial. sub WHATEVER () { ...your value... } And its faster, too. Loading constant.pm and going through its various hoops probably costs you more than the savings of using a constant. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Just ca

Re: [ANNOUNCE] Test::Symlink

function in Test::Builder. Its not clear from the docs what the arguments being checked for sanity means. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Just call me 'Moron Sugar'. http://www.somethingpositive.net/sp05182002.shtml

Re: [ANNOUNCE] Test::Symlink

gree. Also foo($source, $destination) is pretty universal. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Just call me 'Moron Sugar'. http://www.somethingpositive.net/sp05182002.shtml

Re: [ANNOUNCE] Test::Symlink

forks. Don't overspecialize. And again, for the uncommon case of wanting a symlink to a file which does not exist you can have a dangling_symlink_ok() function. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Ahh email, my old friend. Do you know that revenge

Re: AnnoCPAN and a wiki POD idea

he same behavior. The little RSS icon in the lower right only gives an option to subscribe to the "recent notes" feed. A daily email digest would be nice for those of us who prefer push and live in our MTAs not our web browsers. -- Michael G Schwern [EMAIL PROTECTED] http://ww

Re: AnnoCPAN and a wiki POD idea

and > > live in our MTAs not our web browsers. > > Did you see Tim O'Reilly's note: So where's the RSS push interface so I don't have to go checking 2983 RSS feeds every day to see if there's anything interesting? Call me a snob, but O(1) is still better than O(

Re: Testing a Script Distributed with a Module

on I am currently developing, namely, the one that > will be placed in 'blib/lib' by 'make'. Do the same thing you'd do from the command line. perl -Mblib xyz.pl -V which translates into: # $^X is the current perl. system("$^X -Mblib

Re: Testing a Script Distributed with a Module

b > structure it's called 'script/' -- no final 's'. The directories in blib have no relation to where the file came from. Non-binary executables always go into blib/script. Binary executables go into blib/bin. -- Michael G Schwern [EMAIL PROTECTED] http://w

Re: Testing a Script Distributed with a Module

y at > the same level as 'blib/' or 't/'. Since you moved down a directory its ../blib. To simplify things you're best of using an absolute path to blib. Use File::Spec->rel2abs to get one. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Don't try the paranormal until you know what's normal. -- "Lords and Ladies" by Terry Prachett

Re: Devel::Cover Problem: testing || for a default value.

ssary. The first way to do this which pops into my mind is a comment. my $foo = $bar || default(); # DC ignore X|0 "Hey, Devel::Cover! Ignore the case where the right side of this logic is false." Ignored conditions would be green, but perhaps a slightly different shade of gre

Re: Devel::Cover Problem: testing || for a default value.

ta-data to the real data the more likely it will be kept up to date. So inline Devel::Cover hints seem the way to go. > Why is it that my TODO list only gets longer? It means your code is popular and people want to use it and everybody loves you!!! Don't call them TODO items, call

<    4   5   6   7   8   9   10   11   12   13   >