Minor comments:

Instead of or as well as Win32::GetOSVersion I'd say provide the result of `ver`.

Neither LIB nor INCLUDE are gcc specific on Win32. They are standard for VC as well.

Instead of umask, it might be interesting on Win32 to see the results of stuff like cacls.

Knowing cwd() would be useful. As would knowing the full paths to things like (n)make, and other tools. Sometimes failure could be occuring because the tools have spaces in their names.

On win32 knowing if the user is an administrator/power user or not would be useful.

Locale settings might be nice. For instance code might be failing because the locale has strange settings for the thousands seperator or the decimal point.

If it was possible knowing the machine localtime as well as a reference time would be good. Although i could imagine this would be a difficult one.

As for prioritization, I'd say that the more info provided the better so prioritize the easiest to add, and defer the harder until the rest are done.

---
$world=~s/war/peace/g

In reply to Re: What should be captured in automated test reports? by demerphq
in thread What should be captured in automated test reports? by xdg

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.