Way Back When, somewhere in the vicinity of
http:[EMAIL PROTECTED]/msg3.html and
http:[EMAIL PROTECTED]/msg5.html we had
some ideas about developing a sane patching process. I have some very
definate ideas now.
Currently, it seems to go something like this:
- Someone has an idea, or
There's an obscure feature of Test::Harness and Test.pm I stumbled on
recently. You can declare that certain tests are supposed to fail,
they represent tests on features which haven't been implemented yet or
bugs which have yet to be fixed. The syntax is alittle weird, but
that can still be fixe
As I said, I'm an awful administrator. I have enough trouble
remembering what I'm supposed to be doing, much less what you all are
supposed to be doing. I also have about skatey-eight thousand other
projects going, and on top of that I'm employed again (fortunately,
its a QA related job... thaaa
ved and making sure things moved forward. It also
involves some Schwern Wrangling, which you're quite good at.
I think that's what I need. A project manager. If anyone out there
actually has experience in any of this, feel free to shout loudly.
> What's actually involved and
On Tue, Feb 13, 2001 at 12:58:22PM -0500, Kurt Starsinic wrote:
> Can this also be applied to tests that are *supposed* to fail?
Not really, todo has a fairly specific meaning and the test is
definately failing and is definately supposed to be fixed.
In your case, all you have to do is this:
On Tue, Feb 13, 2001 at 01:28:02PM -0500, Kurt Starsinic wrote:
> I'd like to do that, but I haven't (yet) figured out how to say
> "perl --exactly-the-command-line-options-this-perl-was-called-with".
> For example, I don't know how to discover the -I options that I was
> called with. Any ide
On Tue, Feb 13, 2001 at 10:06:58PM +0100, Paul Johnson wrote:
> I'm not sure whether you're talking about the API or the textual output
> here.
The textual output and, to a certain extent, Test.pm's API.
http://mailarchive.activestate.com/mail/msg/perl5-porters:464006 has
the details.
On Thu, Feb 15, 2001 at 07:29:05AM -0500, barries wrote:
> What's the benefit of maintaining a count? Perl's a lot better at it
> than I am.
This was already discussed on p5p (I think) but I'll repeat the basic
arguments here.
Why have Perl maintain the count? Its lazier, some tests don't have
Sorry, DNS glitch. Send them along again.
Sorry, I didn't make myself clear on the "mailing list organization" bit.
What the job really is, someone to spot out-of-control threads (for
instance, the "par" discussion on perl6-language), split off a new
mailing list for it (by requesting from Ask), appointing a chair
(probably the person wh
On Thu, Feb 15, 2001 at 01:38:22PM -0500, barries wrote:
> What do folks think of adding something like the following to Test.pm:
>
> This would make for very succinct easy to maintain test suites, if your
> test suite is simple enough:
>
>use Test qw( do_tests ) ;
>
>do_all_tests(
>
(To those CC'd, you all either maintain or have at some point written
a Perl coverage tool or profiler).
As part of the QA process we need to do alot of test coverage analysis
and, to a lesser extent, performance profiling. Our existing tools
(Devel::Coverage, Devel::DProf, Devel::SmallProf) ar
On Fri, Feb 16, 2001 at 12:14:43AM +0100, Paul Johnson wrote:
> Well, I think a real coverage tool is bit more than that really. All
> the world is not statement coverage. In fact, although it is much
> better than nothing, statement coverage is a fairly weak coverage
> metric. Ideally we would
On Thu, Feb 15, 2001 at 07:56:46PM -0500, barries wrote:
> It's no more difficult to learn except for having to deal with closures.
Closures are not an easy thing to learn. Trust me, I've been trying
for the past few months.
> Indeed, parts are simpler: both the current skip() and the proposed
On Thu, Feb 15, 2001 at 10:18:14PM -0500, barries wrote:
>do_all_tests(
> get_data_set => sub {$data_set = get_data_set() ;
> ok( $data_set ) },
>data_set_type => sub {ok( ref $data_set, "ARRAY" ) },
>data_set_size
On Thu, Feb 15, 2001 at 11:59:24PM -0500, barries wrote:
> > todo({ $obj->fooble == 42 });
>
> Cool. is that a HASH ref
No, CODE. todo would be prototyped (&;$$) or something like that.
With a & prototype, the "sub" is unnecessary to pass an anonymous sub
(think map and grep).
> > This
On Fri, Feb 16, 2001 at 04:53:19PM -0500, barries wrote:
> > > What about providing a module that wraps both Pod::Tests and
> > > Test::Harness, scans the command line and tests any specified modules?
> >
> > Well, same problem with a MakeMaker patch-- everyone will have to have
> > that module.
A new mailing list is available for discussing Perl metrics, coverage,
profiling and other types of automated analysis with the goal of
producing new tools and improving existing ones, as well as large
scale periodic analysis of existing Perl code (read: core libraries &
CPAN).
Move the coverage/
[EMAIL PROTECTED] has been created to cover this field (and to
reduce the CC list). Please subscribe and send all replies to this
thread that way.
I've wedged coverage analysis into Test::Harness (not quite ready for
release yet) and ran it over Perl's core test suite to see how well
the core modules are covered. I'm not 100% sure about this data,
Devel::Coverage needs alot of work and reported alot of false
negatives, but I think I can mak
Alot of the modules in the core have (or had) double lives on CPAN.
Alot of the tests are enormous. And t/ is, in general, something of a
mess.
Part of the problem is its fairly flat directory structure. t/ is
broken up into only a few subdirectories:
base, cmd, comp, io, lib, op, pod, pragma.
On Sat, Feb 17, 2001 at 10:55:29AM -0600, Jarkko Hietaniemi wrote:
> On Sat, Feb 17, 2001 at 10:22:13AM -0600, Jarkko Hietaniemi wrote:
> > > One additional point to consider and solve is the BEGIN 'preamble' we
> > > now add to each test to make certain we are in a known directory, and
> > > more
On Sat, Feb 17, 2001 at 07:49:37PM +, [EMAIL PROTECTED] wrote:
> >A simpler idea would to alter t/TEST so that it runs the tests as
> >"perl -I../lib". This isn't *quite* the same as @INC = '../lib', but
> >it should be close enough.
>
> It isn't. More than once we have things "pass" for _us
Why is t/TEST anything more than a thin wrapper around Test::Harness?
It contains a partial reimplementation, but is missing some very
useful features, such as skip and todo tests. I particularly miss
todo tests. There's alot of little bugs which people mention and then
are forgotten, I'd like t
And what the hell is t/UTEST? Looks like its for unicode. Ok, fine,
but I don't like the code duplication. In fact, it already looks like
the two are falling out of sync.
Case in point, "make utest" still breaks under the 'ok 1 - name'
style. It was never patched along with TEST. Additionall
On Sat, Feb 17, 2001 at 09:08:15PM -0600, Jarkko Hietaniemi wrote:
> I think it was supposed to be TEST with -Mutf8, basically.
> Why it was a separate script? Beats me.
Well, its not anymore. I've added a -utf8 flag to t/TEST and
elminated t/UTEST. make utest still works.
Here's a patch of t
On Sun, Feb 18, 2001 at 04:44:05AM +, Simon Cozens wrote:
> On Sat, Feb 17, 2001 at 09:46:31PM -0500, [EMAIL PROTECTED] wrote:
> > Why is t/TEST anything more than a thin wrapper around Test::Harness?
>
> Because of potential fragility. If Perl isn't entirely together when
> you're running th
+
+=item C
+
+Harness sets this before executing the individual tests. This allows
+the tests to determine if they are being executed through the harness
+or by any other means.
+
+=back
+
=head1 SEE ALSO
-L for writing test scripts and also L for the
-underlying timing routines.
+L for writin
Part of the reason I'm going all this work on Test::Harness is because
I'm going to need the new features for my next job (altruism isn't
dead, its just lying bleeding on the floor).
As such, I need the new Test::Harness *without* having to use
bleedperl. Judging from the discussion on perl-qa
I was poking around on CPAN and noticed this rather complete
alternative to Pod::Tests for embedding tests in code, a bit closer to
what Barrie was discussing.
I've invited the author onto the list and hopefully he'll say a few
words. I'd also like people to poke around with it, see what its all
On Sun, Feb 18, 2001 at 10:39:54AM +0100, Andreas J. Koenig wrote:
> Thanks! I've registered you as maintainer on PAUSE, so that the
> indexer will pick your uploads of Test::Harness in the usual way.
I had a feeling you'd be all too eager to get it off your hands. ;)
I've looked at Test::Harnes
As discussed eariler in
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-02/msg00908.html
I've added t/TestSetup.pm and made t/TEST use it. I had to be careful
to do "-I. -MTestSetup" or else modules which used taint would not work.
A few tests which used do EXPR assumed that '.' wo
Carp has almost no explicit coverage in the core tests. Now, before I
go ahead and write up a test, does anyone have some old tests lying
around from the Olden Days of Yore?
On Sun, Feb 18, 2001 at 07:20:55PM +, [EMAIL PROTECTED] wrote:
> <[EMAIL PROTECTED]> writes:
> >Why is t/TEST anything more than a thin wrapper around Test::Harness?
>
> Because t/TEST pre-dates Test::Harness by years, and no one has got
> round to changing 'make test' call the new style.
I
I'd like to set up automated daily build and smoke tests for bleedperl
and the other active trees.
If anyone's not familiar, a daily build and smoke test is the practice
of building the entire system and running its tests every night to see
if anything was broken durning the day's work. Turn it
On Sun, Feb 18, 2001 at 11:33:52PM +, Nicholas Clark wrote:
> On Sun, Feb 18, 2001 at 06:26:00PM -0500, [EMAIL PROTECTED] wrote:
> > I'd like to set up automated daily build and smoke tests for bleedperl
> > and the other active trees.
>
> How many configuration permutations were you proposin
with some spare CPU ticks, and RC5 has gotten
old, step forward. The weirder the setup the better.
Subscribe to [EMAIL PROTECTED] (or [EMAIL PROTECTED]
for help). Archive is at http:[EMAIL PROTECTED]/
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Pe
ken :-).
Bad things, Mikey. Bad things.
Since TEST does pretty much everything I need now, I'm going to not
poke this at the moment.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
st resting here doing nothing.
We should have something that you can just drop into cron or at or
Task Scheduler or whatever it is you use shortly. Meantime,
subscribe to [EMAIL PROTECTED] is active.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Qual
No. This is silly. End of discussion.
PS I'm also an active non-smoker.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
maged.
Run ./perl -Ilib -d:Coverge t/lib/dumper.t (assuming Devel::Coverage
is somewhere in PERL5LIB) and you get t/dumper.t.cvp with everything
commented out. Even so, there's no mention of Data::Dumper.
Methinks there's still a few bugs in the system.
--
Michael G Schwern <
Just trying to keep things organized. I'm also trying to keep the
volume of mail down on both perl-qa and what must be read by a smoker
(guess THAT one didn't work). Alot of people said along the lines of
"I have a spare machine, but not alot of time..."
--
Michael G Schwer
;
> A perl 'make test' would run the perl test suite and then do a 'make test'
> in each of the ext/* modules.
>
> Why not follow that path?
That makes it much more difficult to produce a simple summary report
of all the tests at the end.
However, I will ponder.
-
ouldn't be installed along with
perl. (Which leaves the possiblity of someone sticking an unrelated
thing in site_perl... but -I. shields against that.)
> PS. perl-qa looks like it goes to p5p, but if it doesn't, cc: me on
> replies.
No, but discussions relevant to both are CC&
best to reconcile these two interface as well as add in names for
tests. Test::ok()'s interface is currently streched to the limit
trying to adapt to all sorts of styles and situations, I don't know if
I can wedge anything more into it. I may have to branch off a new
testing module and le
esting objects at runtime to be worth the slowdown in many cases.
See Carp::Assert for an example of how to do exactly just that (and
the problems involved).
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
ing at the number on the tarball), but the
simple work-around is just to stick $VERSION='0.13' (or whatever) into
lib/Test/Unit.pm.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
eah.pmSample data for find.t
+t/pod/test_pods/lib/Pod/Rhubarb.pod Sample data for find.t
+t/pod/test_pods/lib/Pod/Stuff.pmSample data for find.t
+t/pod/test_pods/pod/perlfoo.pod Sample data for find.t
t/pragma/constant.tSee if compile-time constants work
t/pragma/dia
So I ran all the .pod and .pm files in the distribution through
podchecker() to look for errors...
schwern@magnonel:~/src/perl-current$ perl -nwle 'print $1 if /^(\S+\.(?:pod|pm))\s+/;'
MANIFEST | xargs ./perl -Ilib -MPod::Checker -we 'podchecker($_, \*STDOUT,
-warnings=&g
t for your embedded tests.
The new versions are:
Test::Simple0.07
Test::More 0.05
Pod::Tests 0.03
and are all on the way up to CPAN as I type. If they haven't made it
to your mirror yet, they can always be gotten from
http://www.pobox.com/~schwern/src/
Revision history for Perl ext
ord. And it looks better
withou the qw() *shrug*
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
On Thu, Jun 14, 2001 at 10:51:10AM +0100, Graham Barr wrote:
> Then try this
>
> use strict;
> use Test::More no_plan;
D'OH!
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
and using no_plan requires you to upgrade
Test::Harness.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
= split /-/, $l[0];
> my $delta = (hex($end)-hex($start));
> $mem += $delta;
> if (!defined $l[5] || $l[5] eq '') {
> $realmem += $delta;
> }
> }
> close MAP;
> ($mem, $realmem);
>
port back to the parent process'
> Test::Builder object?
forking and IPC are not my bag, so I don't know what's possible and
what's not. If you can do something to coordinate the parent and
child objects which works everywhere, send a patch. But I don't know
if IPC is portable.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
On Mon, Feb 10, 2003 at 07:21:39PM +0400, Vlad Harchev wrote:
> But anyway, they more big packages will be recommended, the better, so keep
> suggesting them :)
Off the top of my head, some well tested modules:
Math::BigInt
Test::More
some of the recent stuff by Abigail
Test::Harness
On Tue, Feb 11, 2003 at 10:46:58AM -0800, Randal L. Schwartz wrote:
> > "Vlad" == Vlad Harchev <[EMAIL PROTECTED]> writes:
>
> Vlad> I'm testing some perl source code transformation tool (kinda
> Vlad> perl source code prettifier).
>
> If you'll allow me access to your source, I can guarantee
On Mon, Feb 24, 2003 at 03:52:29PM +, Mark Fowler wrote:
> For a module I'm doing at work, I want to check that the correct files
> have been written (and no extra files have been written) in a directory.
>
> Other than writing lots of is(-e based code, is there a simple way to do
> this? I h
As comes up pretty often, people want to trap stuff on STDERR. I've got
adhoc stuff to do that in TieOut.pm, but I've never really found a good
place to put it in a module.
Test::Warn seems like its a good spot. Warnings and stuff going directly
to STDERR are related beasts. So if Janek wants
On Thu, Feb 27, 2003 at 05:32:42PM +, Fergal Daly wrote:
> I think that although a test that ignores blessed classes could be handy in
> some circumstances (ie programming in general), I reckon in the context of
> test suites it's a bug.
I am already not yet convinced. In particular, it mak
On Thu, Feb 27, 2003 at 09:21:09PM +, Fergal Daly wrote:
> > I am already not yet convinced. In particular, it makes this sort of test
> > more difficult than it needs be:
> >
> > is_deeply($obj, { foo => 42, bar => 23 });
>
> Absolutely, but there is currently no way to do this
>
> is_d
On Thu, Feb 27, 2003 at 10:03:50PM +, Fergal Daly wrote:
> > > - let _deep_check take it's cue from the second argument. If the second
> > > argument is blessed then be strict about the classes, if it's unblessed
> > > then ignore the classes. This should happen at all levels in the
> > > stru
On Mon, Mar 03, 2003 at 02:33:32PM -0600, Andy Lester wrote:
> There's a new Test::Pod in town, and it uses Sean's Pod::Simple instead
> of Pod::Checker.
>
> Details at http://use.perl.org/~petdance/journal/10867
>
> Comments welcome, of course.
The old pod_ok() will still work, but the hooha
On Fri, Feb 28, 2003 at 11:51:07AM +, Adrian Howard wrote:
> Option three.
>
>isa_ok($obj, 'MyClass');
>is_deeply($obj, { foo => 42, bar => 23 });
This is, unfortunately, shallow. It won't compare objects inside $obj.
On Fri, Feb 28, 2003 at 11:40:52AM +, Adrian Howard wrote:
> I always meant to revisit the idea for Test::Output which was intended
> to be a generic FILEHANDLE output testing module. Allows you to do
> things like:
>
> output_is { hello() } "hello world\n", STDOUT, "hello world";
> outp
On Tue, Mar 04, 2003 at 09:19:57AM -0600, Andy Lester wrote:
> > Not sure how I feel about this. If you were still using Pod::Checker,
> > I'd
> > definately say it won't fly since it throws so many silly warnings.
> > You
> > mentioned a few, the "Empty Paragraph" and that you can't use "=item
I'm writing a test which does basic checks on all the code in a repository.
It checks that all scripts and modules compile without warnings. I also
want to check that all the POD has no errors or warnings. However, a
lot of the code has no POD. I don't want to write all the POD right now,
but I
On Sat, Oct 04, 2003 at 09:38:11PM +0200, Paul Johnson wrote:
> Who are these people who change directories and don't put things back
> as they found them? ;-)
File::chdir
On Sat, Oct 04, 2003 at 11:00:33PM +0200, Gabor Szabo wrote:
> But what are those numbers and colors in the columns ?
> I could not find in the documentation. Please point me to the
> description if it is available somewhere.
Percentage of the code covered, I think.
removing it).
This is a possibility for perl's internal docs, but its kind of a pain
fr external stuff. Perhaps we can distribute perl's internal docs
with the '=for example' built in (since if you install the docs you
should also install the new POD utilities) and provide
by that's okay its just the autochecker
making a mistake."
On the issue of compatibility, we can use a POD autoconverter as Tim
suggested to translate the '=for example's into C<> as part of the
release (or build) process. This avoids the necessity of patching all
the PO
barfoo');
=pod
We state that Perl does something in the docs and we put a test right
after it (or near it).
This isn't any sort of WONDERTEST but I'm trying to start small
and solve the problems I know we can solve with the least amount of
effort.
--
Michael G Schwern htt
If you missed it, Ask has mail archives for this list up on
http://tmtowtdi.perl.org/.
Yay Ask!
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
make a channel called Perl, and infest
m up, if Perl 6 wants a formal spec, then that's the spec.
But we'll always have the regression suite to fall back on.
PS I'm trying to keep QA RFC discussions on perl-qa rather than
bootstrap.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just
esting the perl6->perl5
translation stuff that's planned.
But you'll note this is perl-qa, not perl6-qa. We're not waiting for
perl6, we want to use this on perl5. Now. Yinz'll just have to catch
up.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PR
On Wed, Jul 26, 2000 at 09:01:22PM -0400, Chaim Frenkel wrote:
> If you do this for new code or changed documentation adding
> a =for result would add more test cases.
Sorry, I don't follow.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Ano
On Wed, Jul 26, 2000 at 09:49:29PM -0400, Clinton A. Pierce wrote:
> Michael G Schwern wrote:
> > In One Sentence
> > ---
> >
> > All code examples in the Perl docs can be at a minimum tested for syntax
> > errors in an automated fashion.
>
>
-qa only. Sorry if I
didn't make this explicit.
> In <[EMAIL PROTECTED]>, Michael G Schwern writes:
> :In One Sentence
> :---
> :
> :All patches to perl must have an associated testing patch.
>
> Can you explain more about how you'll test documentat
was actually a subtle hint that YOU might want to write an RFC on it. ;)
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
The adverse effect is your bone cells will try to grow back to its o
27;t make it anyting but easy to write POD.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
Sometimes these hairstyles are exaggerated beyond the laws of physics
- Unknown nar
ewers and yet has special meaning to certain viewers.
=begin also /=end also works similarly
for arbitrary blocks.
Barrie, you suggested it, so its your babe now! You have the option
to sketch out a new RFC and start working on this or punt the
responsibility to somebody els
rs to help
new code patchers along in authoring tests. There is the problem of
teaching how to write a proper test, since I think there's little
practical experience out there, and also convincing people that the
tests are necessary and we're not just being anal-retentive.
--
Michael G Schw
decide how they want
things spec'd. Should they decide the regression tests should be the
spec, we'll have one ready and waiting! If not, we still have a nice
set of tests.
Maybe I shouldn't even have brought it up.
--
Michael G Schwern http://www.pobox.com/~schwern/
On Thu, Jul 27, 2000 at 03:08:43PM -0400, Barrie Slaymaker wrote:
> Michael G Schwern wrote:
> > Regression tests should be embedded in the code and documentation near what
> > it is they're testing.
>
> s/embedded/embeddable/ and I'm there. I don't think you
On Thu, Jul 27, 2000 at 09:46:05PM -0400, Barrie Slaymaker wrote:
> > > P.S. Why is this perl-qa? Shouldn't it be perl6-qa?
> >
> > I believe Schwern has already answered that ...
>
> I think we have here our first FAQ :-).
GREAT IDEA! Its yours! Organize a
Group/RFC process we're
> inventing.
Why distinct?
BTW Does QA need QA? Should there be a formal way to make sure that
QA is doing its job?
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwal
really done much coverage
analysis. Would someone with time and experience step forward and
take responsiblity for it?
PS In case people aren't aware, there's Devel::Coverage.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid C
a bit.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
But why? It's such a well designed cesspool of C++ code. Why wouldn't
you want to hack mozilla?
-- Ziggy
nal attention.
Either way, start collecting FAQs.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
make a channel called Perl, and infest it with joking and
funit doesnt make alot of sense.
rt us to uncovered portions of code.
> Also, I expect that some of the people willing to work on QA for perl6
> will have access to commercial tools. I have access to Pure Coverage
> for Solaris and am certainly willing to run tests and post results.
Sure! Need all the help we can ge
On Fri, Jul 28, 2000 at 07:49:59PM -0500, Jonathan Scott Duff wrote:
> On Fri, Jul 28, 2000 at 06:25:43PM -0400, Michael G Schwern wrote:
> > 3) =begin preamble/=end preamble/paragraph to test is compatible, but its
> > kind of annoying to write (or even explain) and will ru
which doesn't have an associated
testing patch as opposed to the current situation (patch now, test
later).
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
turds slide easily
spoo
o have bugs.perl.org. Anyone know the state of that?
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
But why? It's such a well designed cesspool of C++ code. Why wouldn't
you want
x27;t apply to them. Rather than attempting to explicitly
enumerate all these special cases, we'll just wrap them up in one meta-case
and note the specifics as they come.
=head2 Independent auditors
CPANTS will be its own thing. While it wll obviously work with CPAN
and the Perl developers, it will be beholden to neither and act as a
wholely independent auditing service. Accordingly, it will have no
direct effect on CPAN or Perl, only whatever influence is granted to
it.
This will hopefully keep CPANTS honest as well as avoid the problem of
appearing to dictate style to authors.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
BOFH excuse #65:
system needs to be rebooted
Experience in large-scale automation.
I'm sure people will be knocking down my inbox to volunteer their
time, RIGHT?
PS CPANTS currently lives at http://www.pobox.com/~schwern/CPANTS/
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just
This was mentioned briefly a while ago. Barrie, are you still up for
maintaining a FAQ?
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
Our business in life is not to succeed but to
splayed. Seemed very natural to me to
wrap X<> around keywords as I wrote them. Yes, we'll have to take
this up with the POD people.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee A
, yes? Not the Makemaker module testing suite. Right?
Reading over this... I have little idea what you're talking about.
Sorry. It seems a little jumbled. Perhaps you could start over and
try again? Possibly not at 1am this time? :)
--
Michael G Schwern http://www.pobox.com/~schw
file_name, $dest_dir ) = @_ ;
> $self->{DEST_DIR} = $dest_dir ;
> croak "No destination directory supplied"
>unless defined $dest_dir && length $dest_dir ;
> $self->parse_from_file( $file_name ) ;
> }
Shouldn't that be $self->
Hey! We've got code! Barrie has Pod::Tests, Pod::AlsoSelect and I
have a prototype for the JART. Where do we put it? We have an
"official" perl 6 repository, or should I just go use Sourceforge?
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTE
1 - 100 of 1868 matches
Mail list logo
