Smylers wrote:
Bram writes:
At the moment foo() returns 3.
Time passes and code changes.
Now there are 3 options:
foo() returns 1, this will result in 'unexpected todo test passed'
being outputted;
foo() returns 3, no special output is produced;
foo() returns 4, no special output is produ
These appear to all being due to the fact that Test::Harness does some very
specific tests of @INC and the environment which Devel::Cover changes. It's
not Devel::Cover's fault.
The below appear to be because Devel::Cover inserts its own blib into @INC and
the tests aren't wired to deal with
Someone who's actually looked at this stuff may want to update
http://en.wikipedia.org/wiki/Test_Anything_Protocol
I think there's also stuff on that page that needs updating
re: Test::Harness 3.
On Tue, May 13, 2008 2:44 pm, chromatic wrote:
> PHP's Symfony has a test framework called lime, base
PHP's Symfony has a test framework called lime, based on Test::More:
http://www.symfony-project.org/book/1_0/15-Unit-and-Functional-Testing
I just heard about a C++ test framework based on lime called lemon:
http://eric.scrivnercreative.com/?p=8
-- c
