, whatever.
Test::Unit's has the idea of Listeners that are responsible for
interpreting the test data and reporting on it. Thus, when you're
running the tests under make test you use a Test::Harness compatible
TestRunner. It works quite well.
--
Piers Cawley
www.iterative-software.com
Sir, yes,
sir! during my talk. I'm raising a QA army.
Hey, I was in that talk and I definitely wasn't yelling 'Sir, yes, sir!'
--
Piers Cawley
www.iterative-software.com
Michael G Schwern [EMAIL PROTECTED] writes:
On Mon, Aug 13, 2001 at 06:13:24AM +0100, Piers Cawley wrote:
Hey, I was in that talk and I definitely wasn't yelling 'Sir, yes, sir!'
You'll be the first against the wall when the revolution comes.
But I thought you were the running dog lackey
the basic test, which would, in
turn, probably mean you could get away with just using Test::More/Simple
--
Piers Cawley
www.iterative-software.com
[EMAIL PROTECTED] writes:
Hi
Is there a step-by-step guide how to create a module with
high kwalitee?
Make sure you don't write a module that does anything really
interesting...
--
Piers Cawley
www.iterative-software.com
Michael G Schwern [EMAIL PROTECTED] writes:
On Mon, Dec 17, 2001 at 08:12:43AM +, Piers Cawley wrote:
What's wrong with
ok ( eval { $foo-isa('Foo') } );
or even:
ok (eval { ref($foo) $foo-isa('Foo') });
As Kurt already pointed out, you can do:
ok
Michael G Schwern [EMAIL PROTECTED] writes:
On Sun, Jan 13, 2002 at 10:04:58PM +0100, Mattia Barbon wrote:
$ bleadperl -MO=-qq,Deparse foo.plx
sub BEGIN {
print foo\n;
}
print bar\n;
If B::Deparse can save BEGIN blocks, B::C can.
I didn't mean that I can't write code to
Michael G Schwern [EMAIL PROTECTED] writes:
On Mon, Jan 14, 2002 at 10:23:46AM +, Piers Cawley wrote:
Um... You're wrong. If you do need 'startup time' initialization then
you should do it in an INIT block. If I may quote from the
documentation:
Like it or not, people put lots of init
