Do you really need to run a gazillion slow tests on every single computer your dist is installed? ...
Don't run extensive "timeout" tests unless you absolutely have to ...
Make your tests as short and fast as possible ... Make more of your tests Author-only tests ...
Thanks for taking the time to report your real world experiences in this area. Very much appreciated.
Though agreeing with Your Mother's sentiment (namely I refuse to criticize devs willing to do things I am not)
I felt very sad about the reception my Perl CPAN test metadata proposal received back in 2010.
Actually, I still feel my suggested declarative trumps imperative approach to CPAN test metadata
is the best general approach to this tricky problem ... though it appears to have little support from the people actually doing the work.
-
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.
|
