Re: Testing What Was Printed

2005-02-12 Thread David A. Golden
Michael G Schwern wrote: On Sat, Feb 12, 2005 at 12:47:56PM -0500, David A. Golden wrote: The trouble with this interface is sometimes you want to collect a bunch of output from a bunch of different functions together. That's why I suggested that it be prototyped to take a code block: stdout_is {

Re: Testing What Was Printed

2005-02-12 Thread Michael G Schwern
On Sat, Feb 12, 2005 at 12:47:56PM -0500, David A. Golden wrote: > >The trouble with this interface is sometimes you want to collect a bunch > >of output from a bunch of different functions together. > > That's why I suggested that it be prototyped to take a code block: > > stdout_is { > fcn1

Re: Testing What Was Printed

2005-02-12 Thread David A. Golden
Michael G Schwern wrote: On Fri, Feb 11, 2005 at 07:30:24AM -0500, David Golden wrote: stdout_is { fcn() } $string, "comment"; # exact stdout_like{ fcn() } qr/regex/, "comment"; # regex match stdout_count { fcn() } qr/regex/, $count, "comment"; # number of matches stdout_found { fcn()

Re: Testing What Was Printed

2005-02-12 Thread Adrian Howard
On 11 Feb 2005, at 19:52, Shawn Sorichetti wrote: [snip] I've started working on Test::Output that is based on Schwern's TieOut module that comes with Test::More. I'm hoping to have it released on CPAN later tonight. Test::Output is a self contained so that it can be included with other modules