Hi all, Forget all the silly debates. I don't want to wait or sit around while we argue over this silly stuff. I'm just going to release some damned code.
Discussions involving clearing scrollback buffers, making people manually page through results (e.g., piping through less), or making people type more by adding "or die" to the end of every test (and thereby ensuring that it's not easy to *dis*able this features) are all fine and have merit, but they're how YOU might like to run tests. Not everyone works that way. I want to run my tests, get a coffee, come back and say "hey, something broke, let's fix it". No manual intervention or extra steps at all. I'm all about choice, regardless of whether or not I happen to agree with that choice. Do I like "bail_on_fail"? No, but I'm going to add it. Frankly, I hardly use Test::Deep, but I'll probably add it (nothing against Test::Deep, I just don't use it). Why would I add these things? Because people are asking for them and it's worth experimenting. I may not get an alpha out today as I've a date and she's far more compelling than you lot :), but when I do, what name do you want? Test::Even::More? Test::Extended? Something else? (This is really the only debate I care about at this point. I'm burnt-out on the rest of it) I'll be supporting using the most common testing modules and optional 'die on fail', 'bail on fail' and 'explain'. Any other 'must have' feature suggestions welcome. See the most recent posts in my journal if you need background. http://use.perl.org/~Ovid/journal/ Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/
