I think this thread is headed towards completely over-engineering this.
For those who really want to customize what gets run when, I think brian's
Test::Manifest solution looks like a winner.
WIth environment variables, I prefer simplicity:
* AUTOMATED_TESTING -- signals that it's *unattended*,
In article <[EMAIL PROTECTED]>, Chris
Dolan <[EMAIL PROTECTED]> wrote:
> On Oct 3, 2006, at 11:13 AM, David Golden wrote:
>
> > Given what you use, perhaps qr/AUTHOR_TEST/ is a good idea.
>
> That's cool. Then I could do C
> in my .t files and just set that to 1 in my .cshrc for all time.
I
* Chris Dolan <[EMAIL PROTECTED]> [2006-10-04 07:20]:
> It should be easy for a 3rd-party developer to glance at the .t
> file and figure out which envvar to use to turn on the author
> tests. I think your abstraction is too obscure.
That’s what POD is for. I agree that adds a layer of indirection
On Oct 4, 2006, at 12:14 AM, A. Pagaltzis wrote:
If it’s worth boilerplating, it’s worth abstracting. How about
use Test::More::ForAuthor [ 'ARISTOTLE' ], plan => 42;
which loads and imports Test::More, then does the exact
equivalent of the boilerplate you showed?
I disagree. It should
* Chris Dolan <[EMAIL PROTECTED]> [2006-10-03 19:35]:
> So, I hereby propose new .t boilerplate:
>
> use Test::More;
> if (!$ENV{AUTHOR_TEST} && !$ENV{AUTHOR_TEST_}) {
> plan skip_all => 'Author test';
> }
> plan ...;
>
> where is either the maintainer's PAUSE username or,
> for la
> Personally, I use TEST_PRIVATE instead to avoid any implied ties like that.
The issue is that you don't want to run author tests for modules you
didn't write. If you're installing Catalyst to write an E-commerce
framework, you don't need to check the POD coverage on Catalyst.
However, you will
Chris Dolan wrote:
> On Oct 3, 2006, at 11:13 AM, David Golden wrote:
>
>> Given what you use, perhaps qr/AUTHOR_TEST/ is a good idea.
>
> That's cool. Then I could do C in
> my .t files and just set that to 1 in my .cshrc for all time.
>
> I've seen discussion of the right env var name has bee
On Oct 3, 2006, at 11:13 AM, David Golden wrote:
Given what you use, perhaps qr/AUTHOR_TEST/ is a good idea.
That's cool. Then I could do C
in my .t files and just set that to 1 in my .cshrc for all time.
I've seen discussion of the right env var name has been batted around
here and on
On 10/3/06, Joshua ben Jore <[EMAIL PROTECTED]> wrote:
Fine, I just didn't feel like inventing a list on the spot. There's a
list of values we know perl uses internally. I see David missed
LANGUAGE, LC_ALL, and LANG.
You'd want to be careful not to do qr/^PERL/ because MACPERL doesn't
match tha
On 10/3/06, David Golden <[EMAIL PROTECTED]> wrote:
On 10/3/06, Alexandr Ciornii <[EMAIL PROTECTED]> wrote:
>
>
> IMHO, including whole %ENV whould be unsafe. We can create list of
> variables to be included. PERL5OPT. Any others? Also maybe
> user-configurable list, where user himself decides wh
On 10/3/06, Alexandr Ciornii <[EMAIL PROTECTED]> wrote:
IMHO, including whole %ENV whould be unsafe. We can create list of
variables to be included. PERL5OPT. Any others? Also maybe
user-configurable list, where user himself decides which variables he
wants to include.
I posted about this r
Hello, Joshua.
Joshua ben Jore wrote:
I'd also like %ENV included in the result. A test in one of my modules
failed on your smoking machine because exists(&main::carp) was true
before it should have been. I'm wondering if you define something like
PERL5OPT=-MCarp=carp,confess,croak because that
On 9/29/06, Alexandr Ciornii <[EMAIL PROTECTED]> wrote:
Hello!
For a long time I'm using Test::Reporter. Now I participate in Vanilla
Perl project (http://win32.perl.org). I've started CPAN smoke.
I've come to several ideas regarding cpantesters. I want your opinion on
them.
1. YAML files on h
* Chris Dolan <[EMAIL PROTECTED]> [2006-10-02 19:35]:
> This ones already possible in a limited sense. I subscribe to
> http://testers.cpan.org/author/CLOTHO.rss
> to see all pass/fail announcements for my modules.
Thanks for the tip – and yay for more vanity feeds. :-)
Regards,
--
Aristotle
On Sep 29, 2006, at 5:16 PM, Alexandr Ciornii wrote:
6. Add posibility to module developers (or anybody) to subscribe to
FAIL reports.
Alex,
This ones already possible in a limited sense. I subscribe to
http://testers.cpan.org/author/CLOTHO.rss
to see all pass/fail announcements for my mo
On 10/2/06, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
CPAN Test reports follow a fairly rigid format that computers can easily
detect. I think it's worth auto-whitelisting messages that look like
"FAIL Foo::Bar 3.14_15" or "PASS Hello::World 2.71". The CPAN::Reporter
(?) and CPANPLUS mails l
> CPAN Testers reports must be sent to the cpan-testers mailing list. As
> with
> most mailing lists, email from non-subscribed addresses is held for manual
> review.
CPAN Test reports follow a fairly rigid format that computers can easily
detect. I think it's worth auto-whitelisting messages t
A. Pagaltzis wrote:
* David Golden <[EMAIL PROTECTED]> [2006-10-02 12:55]:
This creates an interesting quandary: subscribe to the list and
be deluged with thousands of emails or don't subscribe to the
list and accept that your test reports won't show up
immediately.
Good mailing list software
* David Golden <[EMAIL PROTECTED]> [2006-10-02 12:55]:
> This creates an interesting quandary: subscribe to the list and
> be deluged with thousands of emails or don't subscribe to the
> list and accept that your test reports won't show up
> immediately.
Good mailing list software gives you the op
On 10/1/06, Shlomi Fish <[EMAIL PROTECTED]> wrote:
On Saturday 30 September 2006 01:16, Alexandr Ciornii wrote:
> 9. AFAIK reports from people not on cpan-testers/AT/perl.org list are
> manually checked. I don't want to subcribe to this list, if I want, I
> read it via NNTP. With http transport
On Saturday 30 September 2006 01:16, Alexandr Ciornii wrote:
> Hello!
>
> For a long time I'm using Test::Reporter. Now I participate in Vanilla
> Perl project (http://win32.perl.org). I've started CPAN smoke.
>
> I've come to several ideas regarding cpantesters. I want your opinion on
> them.
>
>
21 matches
Mail list logo
