Re: New testing tool in the new Test::Harness

The ideal way for me to develop would be to code up some functionality, document that functionality and create a test case somewhere.

I get sick and tired of calculating how many tests a file has and changing that plan value at the top to reflect it.

How does this framework compare with Test::Unit?

How possible is it to require [cpan://Test::Harness} in a Makefile.PL and then run the test suite using it instead of Tests::More?

Hey, from a CPAN search for Test::Harness it looks like POE uses it. Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality

Comment on Re: New testing tool in the new Test::Harness Select or Download Code

Replies are listed 'Best First'.
Re: Re: New testing tool in the new Test::Harness by chromatic (Archbishop) on Nov 08, 2003 at 01:10 UTC
Test::Harness is not a testing framework. It's a test reporting framework. Test::More (well, Test::Builder) produces output expected to be interpreted by Test::Harness. Test::Unit has its own test reporting framework, though that's really not the point. It could use Test::Harness. I don't know what you're on about regarding `Makefile.PL` as you've described exactly what the default `Makefile` produced actually does. As for counting tests, why not just run the test file, make sure everything passes, and then change the `no_plan` option to `plan`? If that's too much work, set a dependency for Test::Harness 2.x and set `no_plan`.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: New testing tool in the new Test::Harness
by chromatic (Archbishop) on Nov 08, 2003 at 01:10 UTC

Test::Harness is not a testing framework. It's a test reporting framework. Test::More (well, Test::Builder) produces output expected to be interpreted by Test::Harness. Test::Unit has its own test reporting framework, though that's really not the point. It could use Test::Harness.

I don't know what you're on about regarding Makefile.PL as you've described exactly what the default Makefile produced actually does.

As for counting tests, why not just run the test file, make sure everything passes, and then change the no_plan option to plan? If that's too much work, set a dependency for Test::Harness 2.x and set no_plan.

[reply]
[d/l]
[select]