Re: Test::Harness with modules that output to STDOUT

2004-10-16 Thread Michael G Schwern
On Tue, 24 Aug 2004 17:47:42 -0700 (PDT), Ovid <[EMAIL PROTECTED]> wrote: > --- Peter Kay <[EMAIL PROTECTED]> wrote: > > Ok, what's the elegent way to ignore/dispose of the output the tested > > module produces? > > What I do whenever this happens is to move the printing code to a subroutine > or

Re: Test::Harness with modules that output to STDOUT

2004-10-16 Thread Michael G Schwern
On Tue, 24 Aug 2004 11:04:50 -0400, Peter Kay <[EMAIL PROTECTED]> wrote: > Ok, what's the elegent way to ignore/dispose of the output the tested > module produces? Tie STDOUT. Look at Test::More's own test suite for examples. http://search.cpan.org/src/MSCHWERN/Test-Simple-0.49/t/lib/TieOut.pm

Re: Test::Harness with modules that output to STDOUT

2004-08-25 Thread Tels
-BEGIN PGP SIGNED MESSAGE- Helo, On Wednesday 25 August 2004 02:47, Ovid wrote: > --- Peter Kay <[EMAIL PROTECTED]> wrote: > > Ok, what's the elegent way to ignore/dispose of the output the tested > > module produces? > > What I do whenever this happens is to move the printing code to a >

Re: Test::Harness with modules that output to STDOUT

2004-08-24 Thread Ovid
--- Peter Kay <[EMAIL PROTECTED]> wrote: > Ok, what's the elegent way to ignore/dispose of the output the tested > module produces? What I do whenever this happens is to move the printing code to a subroutine or method and override that to capture the output. So if I have something like this:

Re: Test::Harness with modules that output to STDOUT

2004-08-24 Thread Adrian Howard
On 24 Aug 2004, at 16:04, Peter Kay wrote: I am attempting to write tests (using whichever Tests::...) for a module that will use Test::Harness. The module outputs to STDOUT (it just does). You might find http://www.mail-archive.com/[EMAIL PROTECTED]/msg01690.html of interest. [snip] So far,