On Mon, Feb 12, 2001 at 11:58:19PM -0500, [EMAIL PROTECTED] wrote:
> 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 fixed as its undocumented. Basically, it looks (or
> it will look) like this:
>
> 1..5
> ok 1
> ok 2
> not ok 3 # TODO fix the hydrospanner
> ok 4
> ok 5
>
> And Test::Harness will determine that a successful test.
Can this also be applied to tests that are *supposed* to fail? I'm
trying to build a test for a module where success means that the process
exits with a non-zero code, and I'm currently stumped on the right way
to do that.
Peace,
Kurt
| "We must look at what others have looked at before and |
| see it like no one has seen it before." --- Galileo |
