Re: How to best have statements execute only during dev/testing?

2006-01-11 Thread Andrew Savige
--- A. Pagaltzis wrote: Additive filters that the same code can run without are sane when used carefully, and they're easy to create if the trigger is a special comment or better yet POD section: Damian's Smart::Comments module filters specially formatted comments and can do assertions and

Re: How to best have statements execute only during dev/testing?

2006-01-11 Thread Matisse Enzer
On Jan 11, 2006, at 4:15 AM, Andrew Savige wrote: Damian's Smart::Comments module filters specially formatted comments and can do assertions and quite a lot more. I especially like the idea of filtered comments - rather elegant solution. Also, we've given some thought to the issue of

how to detect that we're running under CPAN::Testers?

2006-01-11 Thread Tyler MacDonald
Hello, Is there any way to tell if my package is being tested automatically under CPAN::Testers? Here's the situation: I have a DBI extension (DBIx::Transaction) whose unit tests currently depend on a valid DSN being available. SQLite makes a good testbed for mock databases, so

Re: how to detect that we're running under CPAN::Testers?

2006-01-11 Thread Sébastien Aperghis-Tramoni
Tyler MacDonald wrote: Hello, Is there any way to tell if my package is being tested automatically under CPAN::Testers? For CPAN smokers based on CPAN::YACSmoke, the answer is: test the presence of the AUTOMATED_TESTING environment variable. See also the following page for more

Re: how to detect that we're running under CPAN::Testers?

2006-01-11 Thread Tyler MacDonald
Sébastien Aperghis-Tramoni [EMAIL PROTECTED] wrote: For CPAN smokers based on CPAN::YACSmoke, the answer is: test the presence of the AUTOMATED_TESTING environment variable. See also the following page for more details: http://search.cpan.org/dist/CPAN-YACSmoke/lib/CPAN/YACSmoke/FAQ.pod

Re: how to detect that we're running under CPAN::Testers?

2006-01-11 Thread Sébastien Aperghis-Tramoni
Tyler MacDonald wrote: Sébastien Aperghis-Tramoni [EMAIL PROTECTED] wrote: For CPAN smokers based on CPAN::YACSmoke, the answer is: test the presence of the AUTOMATED_TESTING environment variable. See also the following page for more details: