On Wed, Oct 17, 2001 at 03:05:08PM +0300, Jarkko Hietaniemi wrote:
> Thanks, applied. If this $ENV{PERL_CORE} scheme works we can ask the
> other dual life citizens to do the same. Will make the pumpkin's life
> much, much, much easier.
The only bit that worries me is now in order to run a core
On Thu, Oct 18, 2001 at 12:07:26AM -0600, chromatic wrote:
> > - Of those covered, a smidge less than half have < 75% statement coverage. - "
> >" " , 20% have < 50% statement coverage.
>
> Is it possible to get an update on this? Writing a new test from
> scratch is generally harder t
On Wed, Oct 17, 2001 at 11:21:58PM -0600, chromatic wrote:
> Test::Smoke handles bleadperl nicely. Is there a tool to download a
> set of modules (say, EssentialModules from the Wiki), to run their
> tests, to collate, and to report the results?
Said beast lives as CPAN::Test
http://magnonel.gui
On Thu, Oct 18, 2001 at 01:01:23AM -0600, chromatic wrote:
> Relying on reliable networking is pretty unportable, and it's really hard to
> get useful test information that way. I coded up some mock objects for
> IO::Socket and IO::Select that made this test much easier.
Yes, this is the right w
On Thursday 18 October 2001 19:43, Michael G Schwern wrote:
> Yes, this is the right way to go! It does rely on knowing that Net::*
> use IO::Socket and fiends^Wfriends, but that's ok.
Anyone who's maintaining the test really ought to glance over Net::Time at
least once.
> If it works out, we
