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 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
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
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 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 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 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 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 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
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 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
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 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
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
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
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]&
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
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
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
- 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
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
;
> 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.
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
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
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
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
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
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]>
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
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.
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
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
: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
= split /-/, $l[0];
> my $delta = (hex($end)-hex($start));
> $mem += $delta;
> if (!defined $l[5] || $l[5] eq '') {
> $realmem += $delta;
> }
> }
> close MAP;
> ($mem, $realmem);
>
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
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
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
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
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
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
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!
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 &
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
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
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
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
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 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
> >>
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.
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.
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
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
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.
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
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
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
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!
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
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
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]>
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.
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
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
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]>
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
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
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 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 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 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 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 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 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 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,
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 Sat, Jun 15, 2002 at 06:00:44PM +0100, Mark Fowler wrote:
> I was, out of curiousity, wondering what happened to these changes as they
> don't seem be in 5.8.0RC1
My time machine's in the shop awaiting a shipment of sky hooks.
(Translation: Arthur's patch came after RC1.)
As for why it's not
On Sat, Jun 08, 2002 at 11:12:40AM -0700, chromatic wrote:
> > > If this dependency information changes, it'll fail a test (or maybe warn)
> > > because there's a potential interface change that Bar.pm may need to
> > > know.
>
> > It looks interesting up to this point. Basically, everytime Bar.
On Sat, Jun 08, 2002 at 10:45:50AM -0700, chromatic wrote:
> Taking an average test suite as an example, we could have 'foo.t' and 'bar.t',
> testing Foo.pm and Bar.pm respectively. Bar depends on Foo, and bar.t mocks a
> couple of methods of Foo.
>
> If bar.t uses Test::Depend, it'll pick up se
http://www.pobox.com/~schwern/src/Test-Harness-2.24.tar.gz
Two bugs.
2.24 Wed May 29 19:02:18 EDT 2002
* Nikola Knezevic found a bug when tests are completely skipped
but no reason is given it was considered a failure.
* Made Test::Harness::Straps->analyze_file & Test::Ha
There was a big discussion about writing a module to make it easier to test
sets and common complex data structures and superceed the paltry eq_*
functions in Test::More.
http:[EMAIL PROTECTED]/msg01369.html
Anyone working towards that?
--
This sig file temporarily out of order.
http://www.pobox.com/~schwern/src/Test-Harness-2.23.tar.gz
One big bug, and the rest are VMS and MPE/iX fixes. Basically, you can't
know what the wait status will look like, you can only pull it appart with
POSIX macros.
Mark, could you confirm?
2.23 Wed May 22 12:59:47 EDT
http://www.pobox.com/~schwern/src/Test-Harness-2.22.tar.gz
Little bug fix release. These are old bugs that only recently became
exposed.
2.22 Fri May 17 19:01:35 EDT 2002
- Fixed parsing of #!/usr/bin/perl-current to not see a -t.
(RT #574)
- Fixed exit codes on MPE/iX
2.21
http://www.pobox.com/~schwern/src/Test-Harness-2.21.tar.gz
Test::Harness 2.20 broke verbose. This release fixes it.
2.21 Mon May 6 00:43:22 EDT 2002
- removed a bunch of dead code left over after 2.20's gutting.
- The fix for the $^X "bug" added in 2.02 has be
http://www.pobox.com/~schwern/src/Test-Harness-2.20.tar.gz
Version jump! What's happened is the last of the vestigal parsing code in
Test::Harness has been eliminated. Test::Harness is now just a big wrapper
around Test::Harness::Straps->analyze_file(). This is good. No more
duplic
e KEY;
chmod 0600, $identity;
# ok, now we should be able to start the rsync download
my @rsync_options = (
'-p',
'--partial',
'--size-only',
);
my $sour
http://www.pobox.com/~schwern/src/Test-Harness-2.04.tar.gz
This release contains the new output style for skipped tests. We'll see how
it goes.
2.04 Tue Apr 30 00:54:49 EDT 2002
* Changing the output format of skips
- Taking into account VMS's special exit codes in
g
so my brane isn't wired to think that way.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
"Let's face it," said bearded Rusty Simmons, opening a can after the
that's a good idea (the particulars of getting the output format would
be interesting), but it will require a lot of internal rejiggering.
With the exception of one feature (HARNESS_TODOFAIL), Test::Harness is
feature frozen for 5.8.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://w
d: I18N::Langinfo or POSIX unavailable
What do people think?
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Kids - don't try this at--oh, hell, go ahead, give it a whirl...
equire ripping apart Test::Harness's formatting
code, not something I want to do this close to 5.8. But if anyone has some
extra energy lying around, they could sweep through the skip messages in the
core tests and just shorten them a bit, that will hold things together for a
while.
--
Michael
uoted string "base" may clash with future reserved word at -e line 1.
>
> P.S. Mike, the same thing applies with your mixin.pm
gotcha
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]>
ew();
@@ -55,3 +61,31 @@
ok($lines[1] =~ /Hello!/);
unlink('foo');
+
+
+# Ensure stray newline in name escaping works.
+$out = tie *FAKEOUT, 'TieOut';
+$Test->output(\*FAKEOUT);
+$Test->no_ending(1);
+$Test->plan(tests => 5);
+
+$Test->ok(1, "ok");
+$T
calar,
I've used a simplified version of your patch and also tested that isa_ok()
honors isa() overrides. Thanks.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
4 WHE
http://www.pobox.com/~schwern/src/Test-Simple-0.43.tar.gz
0.43 Thu Apr 11 22:55:23 EDT 2002
- Adrian Howard added TB->maybe_regex()
- Adding Mark Fowler's suggestion to make diag() return
false.
- TB->current_test() still not working when no tests were run via
t; : "not ok\n"' });
}
use File::Find;
find(\&test , shift || '.');
adjust as necessary. Doesn't have to be fancy.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
sun readdened wheat stalks
bowing down in autumn sun
my mind wanders far
-- stimps
http://www.pobox.com/~schwern/src/Test-Inline-0.15.tar.gz
One bug fix, one hack.
First, the line numbers reported by the tests are now correct. So
when it says the test failed on line 198, the test failed on line 198
and not 197. The way I did it is sort of nasty, but it works.
Second, I&#
ns above and beyond Test::More. One
of these is fresh_perl() which runs a given chunk of code in a fresh
Perl process in a cross-platform manner. It's usually used to test
code that will cause a segfault, but's useful for what you want, too.
I've been meaning to make a CPAN versi
ived set objects
we'd be Smalltalk. TMTOWTDI. Live it. Love it. Work with it. Send
lamentations to the contrary to comp.lang.perl.misc. :)
(Really the whole problem could never had arisen if you hadn't let an
ECE dropout redesign Perl's testing infrastructure ;) )
--
is_deeply().
Again, they are *NOT TEST FUNCTIONS*. They produce no diagnostics.
They are just normal comparision functions and becoming more and more
out of place in Test::More.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl Qu
On Thu, Apr 11, 2002 at 10:37:10AM +0900, Curt Sampson wrote:
> On Tue, 9 Apr 2002, Michael G Schwern wrote:
>
> > > I'm not sure exactly what the purpose of this is; your test will
> > > still fail if it dies even when not in a lives_ok block, right?
> >
>
1 - 100 of 413 matches
Mail list logo
