I've been writing a new testing module and testing it with Test::Builder::Tester. During this I've found a few annoyances and problems with using tbt. I've made quite a few extensions to the code which has resulted in another release.
Latest version (0.07) at http://2shortplanks.com/temp/tbt/ Changes: - test_fail function that is a convenience method for declaring a standard "# Failed ..." line with test_err - test_diag function that is a convenience method for declaring things with test_err that would have been output with tb's diag function. - More meta tests (i.e. tests that test that tbt itself works.) The output of tbt's diagnostics functions are actually checked to make sure they're correct. Yes, this was really hard to do. - Bonus colour mode that uses Term::ANSIColor (if you have it and you explicitly enable colouring) that colours the output to disambiguate debug information printed by tbt and that that is quoted debug information from the original test module you are testing Questions: Do we like these changes? Should I keep them or are they too excessive. Anyone want to test these on other platforms? I've tried it on perl 5.6.1 on Linux. I'd really like to see that it still works on a system that doesn't have Term::ANSIColor installed on it (it should turn colouring into a no-op and skip tests, but I can't test that.) Later. Mark. -- s'' Mark Fowler London.pm Bath.pm http://www.twoshortplanks.com/ [EMAIL PROTECTED] ';use Term'Cap;$t=Tgetent Term'Cap{};print$t->Tputs(cl);for$w(split/ +/ ){for(0..30){$|=print$t->Tgoto(cm,$_,$y)." $w";select$k,$k,$k,.03}$y+=2}
