On Tue, Dec 16, 2008 at 06:37:30AM +0100, Ulrich Habel wrote:
> Hi,

Hi,

Thanks for participating!

I'm not that familiar with CPAN::Reporter based smoke testing 
( someone else who is bound to respond soon ), but I do have
a couple of hints.

> 
> I just set up my toolchain as described in:
> 
> http://wiki.cpantesters.org/wiki/CPANReporterSmokerLong
> 
> My config.ini for the reporter looks like this:
> 
> hobbes# more .cpanreporter/config.ini
> edit_report=default:ask/no pass/na:no
> email_from=Ulrich Habel <[email protected]>
> send_report=default:ask/yes pass/na:yes
> smtp_server=localhost
> 
> 
> I started the smoker and it builds and tests like crazy. I've set the 
> mailserver on localhost to queue all the mails and what I am missing 
> right now are the mails.

Check that CPAN itself is configured to use CPAN::Reporter

o conf test_report 

> 
> It created 2 mails about my environment so far - but nothing more. When 
> will all the mails be sent? When will the reports be generated? Does it 
> take a full build of all the modules to create something like a report?

It should be generating a test report after each set of tests are run.

> 
> The documentation inside the wiki lacks a basic workflow overview - what 
> happens when. I'll provide it when I understood the mechanism. The 
> manpages/pod documentation is very short and basically describes what 
> the module does internally. Providing a documentation with a broad 
> picture might be nice. I am willing to write additional documentation - 
> feed me :)

Adam Foxson wrote up a general overview of CPAN Testers and released it as
a module CPAN::Testers:

http://search.cpan.org/~fhoxh/CPAN-Testers-0.02/lib/CPAN/Testers.pm

I have the slides from a talk I gave at YAPC::EU 2008 that have some diagrams 
showing
some of the 'workflow':

http://www.kidney-bingos.demon.co.uk/CPAN_Testing/

Cheers,

-- 
Chris Williams
aka BinGOs
PGP ID 0x4658671F
http://www.gumbynet.org.uk
==========================

Attachment: pgpOi1QOU4KOQ.pgp
Description: PGP signature

Reply via email to