-BEGIN PGP SIGNED MESSAGE-
Moin,
On Monday 14 November 2005 18:21, Chris Dolan wrote:
Hello all,
I've just published an article about public vs. private regression
tests. I've defined private tests as t/*.t files that are for the
author only and don't go in MANIFEST. Naturally
On Tue, 2005-11-15 at 15:23 -0600, Chris Dolan wrote:
After reading some of the insightful comments posted on my blog, I've
been convinced that the private tests should be included in the CPAN
distribution, but disabled in some way (perhaps via a file extension
other than .t
Le mardi 15 novembre 2005 à 15:23, Chris Dolan écrivait:
After reading some of the insightful comments posted on my blog, I've
been convinced that the private tests should be included in the CPAN
distribution, but disabled in some way (perhaps via a file extension
other than .t
Philippe 'BooK' Bruhat wrote:
Le mardi 15 novembre 2005 à 15:23, Chris Dolan écrivait:
After reading some of the insightful comments posted on my blog, I've
been convinced that the private tests should be included in the CPAN
distribution, but disabled in some way (perhaps via a file
Adam Kennedy wrote:
What about a special environment variable, like RUN_PRIVATE_TESTS?
I've been working on a concept of taggable tests on some of my larger
commercial stuff, integrating with the Test::More skip() function, and
some form of environment variables does indeed seem the best
On Tue, 2005-11-15 at 22:33 -0600, Chris Dolan wrote:
Beware that M::B has a recursive mode for finding tests. It's set by
the author, so you should be safe in this case, but it's a point
worth remembering.
I haven't looked at the code again just now, but wouldn't overriding
Hello all,
I've just published an article about public vs. private regression
tests. I've defined private tests as t/*.t files that are for the
author only and don't go in MANIFEST. Naturally, those don't get as
much publicity as tests included in CPAN distributions.
In the article I
