http://qs1969.pair.com?node_id=733675


in reply to cpanplus - Test::Reporter could not resolve ....

cpan can send test reports also; but I have yet to send a report successfully. Perhaps it does not authenticate with the mailserver of my provider ...

Anyhow, there seems to be a possibility to send the test reports through HTTP, but it is largely undocumented and nowhere I could find the URL to link to and deliver the report. A real pity, as I think we would see a lot more testers if there was a real simple way of delivering the reports.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

  • Comment on Re: cpanplus - Test::Reporter could not resolve ....

Replies are listed 'Best First'.
Re^2: cpanplus - Test::Reporter could not resolve ....
by xdg (Monsignor) on Jan 14, 2009 at 18:58 UTC
    nowhere I could find the URL to link to and deliver the report

    The HTTP gateway code is proof of concept still. People would have to run their own server to receive reports and send on via SMTP. There have been discussions of getting someone to volunteer a server and maintenance to run a public gateway.

    In the meantime, work creeps forward in support of "CPAN Testers 2.0" which will be entirely HTTP based. It's one of the projects planned for the QA Hackathon this March. We hope we can get it released before Christmas. ;-)

    -xdg

    Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

      We hope we can get it released before Christmas
      Nice, it will be published together with Perl 6 then! ;-)

      CountZero

      A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James