I was just cleaning up old mails when I found this thread
On Tue, Jun 10, 2008 at 2:49 PM, David Golden [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 12:28 AM, Gabor Szabo [EMAIL PROTECTED] wrote:
The issue I am trying to solve is how to catch and report
when a test suit gives any
On Tue, Aug 19, 2008 at 3:11 PM, David Golden [EMAIL PROTECTED] wrote:
On Tue, Aug 19, 2008 at 8:02 AM, Gabor Szabo [EMAIL PROTECTED] wrote:
Sure. IMHO that is what *diag* is for.
To print all kinds of messages to the screen in a TAP.
Going up the thread, I think you had asked about whether
--- Gabor Szabo [EMAIL PROTECTED] wrote:
So I wonder if there are other ways. E.g. if the harness could catch
the warnings?
The harness has code which can allow you to merge the STDERR and STDOUT
streams. See the '--merge' switch to prove. With that, a
(simple-minded) parser becomes:
2008/6/10 Gabor Szabo [EMAIL PROTECTED]:
So apparently using Test::NoWarnings isn't that cool
and mandating it with CPANTS metric is even less cool.
What's the problem with T::NW? Maybe I'm misunderstanding the rest of
this mail but you seem to be looking for something that will catch
warnings
On Tue, Jun 10, 2008 at 10:33 AM, Fergal Daly [EMAIL PROTECTED] wrote:
2008/6/10 Gabor Szabo [EMAIL PROTECTED]:
So apparently using Test::NoWarnings isn't that cool
and mandating it with CPANTS metric is even less cool.
What's the problem with T::NW? Maybe I'm misunderstanding the rest of
On 10 Jun 2008, at 08:14, Ovid wrote:
So I wonder if there are other ways. E.g. if the harness could catch
the warnings?
The harness has code which can allow you to merge the STDERR and
STDOUT
streams. See the '--merge' switch to prove. With that, a
(simple-minded) parser becomes:
use
On Tue, Jun 10, 2008 at 3:33 AM, Fergal Daly [EMAIL PROTECTED] wrote:
What's the problem with T::NW? Maybe I'm misunderstanding the rest of
Not a problem with T::NW itself, just that it doesn't catch all the
cases that Gabor is concerned about and people had issues with using
CPANTS to encourage
On Tue, Jun 10, 2008 at 12:28 AM, Gabor Szabo [EMAIL PROTECTED] wrote:
The issue I am trying to solve is how to catch and report
when a test suit gives any warnings?
Are there situations where a test suite should give warnings? I.e.
stuff that the user should see that shouldn't get swallowed
I haven't used Test::NoWarnings. However, for me personally, I don't
like to suppress output unless I am catching it in an explicit test. The
code I am working on is designed to throw warnings or errors under
certain conditions. Especially in code that is designed to run under a
web server, it is
In article [EMAIL PROTECTED],
Gabor Szabo [EMAIL PROTECTED] wrote:
Having those warnings during tests is a problem that should be somehow solved.
I'd like to have a cpan-testers report whenever my test suite issues
warnings. It's not a new category. If the tests all pass it's still a
PASS.
On Monday 09 June 2008 21:28:40 Gabor Szabo wrote:
The issue I am trying to solve is how to catch and report
when a test suit gives any warnings?
Is it even possible? I thought one of the goals of CPANTS was not to run any
of the distribution's code directly. The most useful metrics seem to
On Tue, Jun 10, 2008 at 7:42 AM, chromatic [EMAIL PROTECTED] wrote:
On Monday 09 June 2008 21:28:40 Gabor Szabo wrote:
The issue I am trying to solve is how to catch and report
when a test suit gives any warnings?
Is it even possible? I thought one of the goals of CPANTS was not to run any
12 matches
Mail list logo
