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
find_test_
David Golden wrote:
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 in
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 way
On Nov 15, 2005, at 3:38 PM, chromatic wrote:
I posted a small Module::Build subclass that shows one way to do
this to
Perl Monks:
http://perlmonks.org/?node_id=508160
Yeah, I saw that one.
Perhaps a better approach is to store these tests in a subdirectory of
t/.
Beware that M::B h
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 (per
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
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
&
results may vary from machine to machine should be public wherever
feasible.
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
-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
le system where authors publish
the results of private tests with their distributions as a trust-
based kwalitee system.
http://www.chrisdolan.net/talk/index.php/2005/11/14/private-
regression-tests/
Both positive and negative feedback is very welcome!
Chris
--
Chris Dolan, Software De
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
11 matches
Mail list logo
