I would 'cd' to the top level WWW::Mechanize::Firefox source directory and re-run those failing test scripts individually:
perl -Mblib t/10-plugin-repl-enter.t
perl -Mblib t/16-plugin-repl-home.t
perl -Mblib t/18-plugin-repl-util-help_url_for.t
perl -Mblib t/19-plugin-repl-util-doc_for.t
perl -Mblib t/20-plugin-json.t
If there's still too much info for the console to neatly accommodate, redirect the output to files, and then peruse those files.
You can install the module anyway, if you wish. You may well find it's quite adequate for your purposes, despite the failing tests. (The choice is yours.)
Should you wish to install it, just run dmake install
from that top level source directory.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||