BKB: An inconsistent review can very well be unhelpful. If you speak highly of a module in the text but rate it poorly numerically, you are being confusing at best and duplicitous at worst. Either quality merits "unhelpful" in my view.
When you write a new process, module, class, interface, method, function, subroutine, program or script, you need to know it works. As the project grows, things almost invariably and inevitably need refactoring. Test::More provides a simple but powerful way of writing test scripts to ensure the integrity of your code through this passage.
Simple and more complex comparative assertions such as "is", "isnt", "is_deeply", and simple integrity checks such as "ok" and "isa_ok" produce a standard output, compatible with the older Test module, as well as the Test::Harness.
If you haven't tried this module, you really ought to give it a go: the clear and friendly tutorial can almost guarantee that you will be happily using the module on production code within the day, and within a week you will see your productivity improve no end.
It used to irk me that the error reporting read "...called at file.t line 248" which differed from the default perl output for (apparently) no good reason, and messed up all my editors; but that small price to pay has now been remedied by the helpful, if somewhat less than graceful, author.
This is almost certainly my most-used distribution. Everything I write that is more complex than a few-liner gets a test or two (or more), and almost all my tests start with Test::More. The interface is straightforward (although a few sub names are slightly confusing) and the tutorial is just right. Learning to use Test::More is a prerequisite for any serious Perl programmer.