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
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
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
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
;
> 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.
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
- 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
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
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
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]&
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
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
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
401 - 413 of 413 matches
Mail list logo
