Devel::Cover only seems able to report on the test suite for a single platform, and not an aggregate coverage across multiple platforms (correct me if I'm wrong)
Paul Johnson describes how to do it here. This has come up a number of times on the perl-qa@perl.org mailing list. On Paul's to do list is to set up a database to collect coverage data from decentralised machines (running different versions of Perl on different platforms) along with a web interface to view this data. I think he is looking for volunteers, so you might like to contact him. ;-)

Oh, and though I'm sure you've thought of this already, one can employ mock objects (for example, Test::MockObject) to improve coverage on all platforms (and make the overall design more "testable").


In reply to Re: Best practice for testing portability modules by eyepopslikeamosquito
in thread Best practice for testing portability modules by rinceWind

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.