Re: Test::Harness skip reason report change?
> On Thu, 25 Apr 2002 23:49:58 -0400, Michael G Schwern <[EMAIL PROTECTED]> said: MS> Sarathy's convinced me that we need a better way to format skip reasons so MS> they don't just run off the end of the screen. After a lot of hemming and MS> hawing on my part, we may have found an easy fix. MS> [..snip..] MS> What do people think? Looks nice. But I'm curious if it will be possible to see skip reasons with new formatting if one test had several different skip reasons. Currently it just emits 'skipped: various reasons'. -- Ilya Martynov (http://martynov.org/)
Re: t/TEST ported to VMS
On Fri, Apr 26, 2002 at 12:13:31AM -0500, Craig A. Berry wrote: > I've finally gotten around to making t/TEST work properly on VMS. > The patch is below and works with bleadperl on VMS and also works as > before on Mac OS X. If this is too ugly or too late for 5.8.0 I can > live with that. However, there are several advantages here for us. Looks good, it's in. -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
Re: Test::Harness skip reason report change?
On Fri, Apr 26, 2002 at 11:39:26AM +0400, Ilya Martynov wrote: > Looks nice. But I'm curious if it will be possible to see skip reasons > with new formatting if one test had several different skip > reasons. Currently it just emits 'skipped: various reasons'. Yes, that's a good idea (the particulars of getting the output format would be interesting), but it will require a lot of internal rejiggering. With the exception of one feature (HARNESS_TODOFAIL), Test::Harness is feature frozen for 5.8. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One You're smoother than a tunnel of shining sorrow.
Re: Test::Harness skip reason report change?
On Fri, Apr 26, 2002 at 11:39:26AM +0400, Ilya Martynov wrote: > Looks nice. But I'm curious if it will be possible to see skip reasons > with new formatting if one test had several different skip > reasons. Currently it just emits 'skipped: various reasons'. on the "looks nice". I hadn't thought of the better list of reasons, but I agree with what that too. However, if there are 50+ different skip reasons, would it be better to have some sort of cutoff on the amount of extra data per test to show. Something like 10, and then it a ... line and tells you to run the test to see the full output? Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/