<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jul 22, 2014 at 1:37 PM, Daniel J. Luke <span dir="ltr"><<a href="mailto:dluke@geeklair.net" target="_blank">dluke@geeklair.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Jul 22, 2014, at 11:51 AM, Mojca Miklavec <<a href="mailto:mojca@macports.org" rel="noreferrer">mojca@macports.org</a>> wrote:<br>
</div><div class="">
> - I'm unable to test 1000 ports.<br>
<br>
</div>we should probably enhance `port test` to be more useful. With the perl modules (at least), they usually have test suites that we should be able to run to verify we're not breaking things - so changes to MacPorts perl could get some tests 'for free'<br>
<div class=""><br></div></blockquote><div><br></div><div>One enhancement for `port test` that I would like to see would be an option to run the test phase automatically instead of having to explicitly call it with `port test`: <a href="https://trac.macports.org/ticket/42731" rel="noreferrer">https://trac.macports.org/ticket/42731</a></div>
<div>Also test phase dependencies would be useful, especially if we are talking about CPAN ports, because I know when using CPAN manually it would often print a message about some dependencies only being needed for testing: <a href="https://trac.macports.org/ticket/38208" rel="noreferrer">https://trac.macports.org/ticket/38208</a></div>
</div></div></div>