<div dir="ltr"><div class="gmail_extra">On Fri, Apr 11, 2014 at 6:52 PM, <span dir="ltr"><<a href="mailto:MK-MacPorts@techno.ms" target="_blank">MK-MacPorts@techno.ms</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 21 Mar 2014, at 00:14 , Ryan Schmidt <<a href="mailto:ryandesign@macports.org" rel="noreferrer">ryandesign@macports.org</a>> wrote:<br>
</div><div class="">> I’m not aware of any ports that do that, or any tests that are designed to work that way.<br>
<br>
</div>Only recently I came across the "test phase” which can be defined in a portfile.<br>
<br>
I’ve introduced properly running tests for kmymoney4-devel with r118839.<br>
The user can build and run the tests by using this sequence:<br>
—<br>
$ sudo port test kmymoney4-devel +tests<br>
—<br></blockquote><div><br></div><div>Yeah, I have noticed that my Portfiles with test phases usually end up with the test phase hidden in a variant like that as well, although in my case it is usually because there is no way to specify dependencies needed just for the test phase: <a href="https://trac.macports.org/ticket/38208" rel="noreferrer" style="color:rgb(17,85,204)">https://trac.macports.org/ticket/38208</a> (which is why I just stick them in a variant instead)</div>
<div><div> <br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Afterwards the user could proceed with<br>
—<br>
$ sudo port install kmymoney4-devel +tests<br>
—<br>
without the tests actually being installed in the system, which the “tests” variant might imply.</blockquote><div><br></div><div>The issue for tests not actually being part of the normal install process is <a href="https://trac.macports.org/ticket/42731" rel="noreferrer">https://trac.macports.org/ticket/42731</a></div>
<div> </div></div></div></div>