comment on

[Minor attribution issue: s/link led to Corion's response/link led to choroba's response/ (2nd paragraph)]

After successful "rm sources/authors/id/?/??/*/CHECKSUMS", I'd suggest the first thing to do would be to upgrade CPAN. As I indicated in "Re: cpan warning for XML::DoubleEncodedEntities", the vulnerability exists in v2.28; it's fixed in v2.29 (I left some notes about that in "Re^8: pod2html: link (L<...>) formatting code (timeloop)"); the current version is v2.34.

"Q1) How can I repeat the tests in a comprehensive fashion?"

For this, I'd generally use the prove utility.

On the Astro::SIMBAD::Client page, there's a direct link to the tarball, there's also a link to the GitHub repository if you prefer that. Unpack the tarball and run the usual "perl Makefile.PL" followed by "make". At this point, the next step would normally be "make test"; instead of that, run prove here.

There are a host of options. Some suggestions:

# Run all tests with verbose output (possibly very lengthy)
$ prove -vb t/*.t

# Run individual test scripts, e.g.
$ prove -vb t/basic.t
[download]

You can run those tests as many times as you want.

I can't see a "Q2) ...?". :-)

— Ken

In reply to Re^3: cpan warning for XML::DoubleEncodedEntities by kcott
in thread cpan warning for XML::DoubleEncodedEntities by Aldebaran

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks