NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
Ovid (2709)
Ovid
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
Tuesday January 25, 2005
01:01 PM
Color Tests
One of former coworkers altered out test suite to output test data with colors. I tried to do that with Test::Builder to make successes show up in green, failures show up in red with the possibility of having skips and todos showing up in yellow or yet another color. I find it very handy. Then I found out how Test::Harness::Straps::_analyze_line figures out if a test fails or passes. Very agonizing, I must say. I'll have to take a look at the iterator and figure it out from there. The test module internals are scary.
Color Tests
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
_analyze_line (Score:2)
--
xoa
Re:_analyze_line (Score:2)
I realize that the internals may change radically and I haven't tried to submit a patch because I doubt anyone would really care about this other than myself.
Re:_analyze_line (Score:2)
Though I confess it's darned handy to scroll through a bunch of test output and see the chunk of red in the sea of green. It makes debugging much faster though I want to look at chromatic's qtest and see what I could modify from there and not have to touch the internals.