Re^3: why Test::More?

App::Prove is a typical harness that is used. Also see make test and build test in the build tool chain.

I have been using (or trying to change my habits to use) Test Driven Development, to minimize the amount of untested code in my codebase. I have been using one .t file per package (well, per .pm file).^*

^* - In reality, I use Test::Class with a unittests.t loader, but that is more of an implementation detail. In effect it is one test file per source file. Test::Class uses inheritance, but I think that test files could also be written using roles.

--MidLifeXis

Comment on Re^3: why Test::More? Select or Download Code

Replies are listed 'Best First'.
Re^4: why Test::More? by tobyink (Canon) on Sep 16, 2013 at 13:00 UTC
App::ForkProve is nice as a more-or-less drop-in replacement for App::Prove. `use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name`	[reply]
Re^4: why Test::More? by Anonymous Monk on Sep 10, 2013 at 16:27 UTC
thank you	[reply]