--- 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:
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,
On Tue, Aug 24, 2004 at 01:51:12PM -0400, David H. Adler wrote:
>
> > (oh, and as an aside I released a new Acme::Test::Buffy, with slightly
> > improved documentation and spelling too - but no one cares about that)
>
> Says who?
*I* care. And you have no idea how stupid I felt submitting an R
On Tue, Aug 24, 2004 at 10:38:50AM +0100, Mark Fowler wrote:
> I released another testing module yesterday:
>
> http://search.cpan.org/dist/Test-DoubleEncodedEntities/
I note that that's not the name in the subject of your mail. I hope
this is the right one. :-)
> (oh, and as an aside I rele
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).
Now, in theory, Test::Harness currently ignores anything that doesn't
start with "ok" or "not ok", but for whatever reason, when I have
"no_plan",
I released another testing module yesterday:
http://search.cpan.org/dist/Test-DoubleEncodedEntities/
It detects strings like 'é' in your HTML, meaning it can detect
the case when you've double encoded your entities.
Anyone who spots any errors - please chuck 'em into RT. Patches agains
