Basically because it ignores Test::Builder, and the modules built with it.
So we have yet another set of testing functions (assert_somethingorother in Test::Extremes case), and no way of adding new kinds of test to the framework easily. Test aren't named either which makes using large test suites a complete pain.
It also slightly annoys me by saying it's in an xUnit style when it doesn't do most of the things that an xUnit framework does (setting up of test fixtures, composition of test suites, etc.). This kind of thing isn't "OO cruft" as it says in the documentation - they're tools that make some kind of testing a lot easier.
If you need things like text fixtures then Test::Extreme won't do the job. If you don't need them then there are better testing tools available with Test::More and friends.
All IMHO of course ;-)
In reply to Re^3: RFC: Runnable test code integrated into Modules.
by adrianh
in thread RFC: Runnable test code integrated into Modules.
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |