Search

Menu

Pages

Users

Help

Tools

Syndication

Our Sponsors

Edsger Dijkstra:

"Program testing can be used to show the presence of bugs, but never to show their absence!"

CPAN Testers is only made possible with the support of our sponsors.
For more information on sponsoring, please visit the
I ♥ CPAN Testers website.

Dyn (pronounced “dine”) is the worldwide Internet Infrastructure as a Service (IaaS) leader, powering Managed DNS and Email Delivery for over four million enterprise clients, small businesses and home users. Simply put, Dyn helps websites run faster and be more reliable, while also ensuring that transactional emails that consumers want and need reach their inboxes. We make the Internet a better place.

The CPAN Testers Wiki site has been upgraded since you last accessed the site.
Please press the F5 key or CTRL-R to refresh your browser cache to use the latest javascript and CSS files.

Smoking With POE

In November 2006, Chris Williams released POE-Component-CPAN-YACSmoke, which used POE to run multiple test environments of CPANPLUS/CPAN-YACSmoke, and coordinate the distribution testing between them. Thus Chris was able to test on multiple versions of Perl and become the most prolific tester in CPAN Testing history.

Chris says, "My main gripe with CPAN::YACSmoke was that if a particular module test 'hung' for some reason it would just sit there for hours until I happened to notice it."

Smoking Blead Perl

So recently I started CPAN smoking using blead perl and had a few requests from other people on how to set up CPAN smoking using bleadperl.

Well I found it is relatively easy to do, since blead perl now includes CPANPLUS.

Here's how you do it:

First off install POE::Component::CPAN::YACSmoke in your system perl using either cpan or cpanp. It is advised that Proc::ProcessTable is installed when prompted. This will install the minismoker script which we will use later on.

Okay. Let's install blead perl.

I usually install my testing perl in the home directory of a non-privileged user account.

This will pull blead perl source down to the current directory. Then run ./Configure. Take the defaults ( or change to taste, such as enabling threading, etc. ), except when prompted for the installation prefix.

If you need to configure cpanp to send test reports through a particular mail relay open up an editor and edit the file: /home/chris/blead/.cpanplus/lib/CPANPLUS/Config/User.pm

Alter the line $conf->set_conf( cpantest_mx => '' ); to specify the dns name or IP address of a suitable relay. Save the file.

Right, back into cpanp and we'll install CPAN::YACSmoke. The current development release of CPAN::YACSmoke won't use our hacked .cpanplus directory so we have to install a hacked version. Also Regexp::Assemble prior to 0.29 fails it's tests on blead, so make sure that you use version 0.29 or greater. ( Thanks to grinder for fixing that ).

Smoking Stable Perl

First off install POE-Component-CPAN-YACSmoke in your system perl using either cpan or cpanp. It is advised that Proc-ProcessTable is installed when prompted. This will install the minismoker script which we will use later on.

Okay. Let's install perl-5.8.8

I usually install my testing perl in the home directory of a non-privileged user account.

Assuming everything went okay we should have perl-5.8.8 installed under /home/chris/perl588

$ cd
$ export APPDATA=/home/chris/perl588/

Setting APPDATA forces CPANPLUS to locate its .cpanplus directory under /home/chris/perl588/. Now let's configure cpan ( only answers different to the defaults are shown ):

$ /home/chris/perl588/bin/cpan
Would you like me to configure as much as possible automatically? [yes] no
CPAN build and cache directory? [/home/chris/.cpan] /home/chris/perl588/.cpan
Policy on building prerequisites (follow, ask or ignore)? [ask] follow
Parameters for the 'make install' command?
Your choice: [] UNINST=1