Re: Stuck on Testing::skip()

2001-03-18 Thread Michael G Schwern
On Sat, Mar 17, 2001 at 01:19:02PM -1000, Tim Jenness wrote: > I think the skip() function should at least add "Skip" to the reason when > printing it - the user of Test.pm should not need to know the format of a > skip message required by Test::Harness. This has already been fixed (with concessi

Re: Stuck on Testing::skip()

2001-03-18 Thread Michael G Schwern
On Sat, Mar 17, 2001 at 10:34:18PM +0100, Paul Johnson wrote: > If we're allowed to mess with the interface, my counter proposal would > be to simplify it rather than complicate or extend it. Concurrent evolution is a beautiful thing. I just wrote Test::Simple last night after a conversation wit

Test::Simple

2001-03-18 Thread Michael G Schwern
Here is the docs for Test::Simple, an extremely basic, extremely easy to learn testing module for those just learning to write tests. It addresses the issue of getting people to write tests *at all*. Forget about todos and skips and halting problems. Those will be addressed in a different modul

Re: Test::Simple

2001-03-18 Thread Michael G Schwern
Looking again at those docs, the example needs to be much simpler. All the OO parts need to be eliminated, as people often get frightened when they see OO. Also, it probably needs more description before we dive into ok(). Test::Simple doesn't require you declare your number of tests. This is a

New Carp::Assert function, affirm()

2001-03-18 Thread Michael G Schwern
So someone on FWP brought up using B::Deparse to display the contents of subroutine references. This, plus the fact that I found myself needing multi-line assertions drove me to write this new function for Carp::Assert. I'm looking for comments before I release this in the new version. =item