<div dir="ltr">One approach you could use for the test output is to redirect it into a file, and then put a ui message to look at that file for the results.<div><br></div><div>David</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Sep 20, 2014 at 2:11 PM, Mark Brethen <span dir="ltr"><<a href="mailto:mark.brethen@gmail.com" target="_blank">mark.brethen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On Sep 20, 2014, at 10:30 AM, Clemens Lang <<a href="mailto:cal@macports.org">cal@macports.org</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> ----- On 20 Sep, 2014, at 16:27, Mark Brethen <a href="mailto:mark.brethen@gmail.com">mark.brethen@gmail.com</a> wrote:<br>
><br>
>> You're thinking it should run automatically instead of user setting?<br>
><br>
><br>
> Setting test.run and test.cmd doesn't make MacPorts run the tests automatically.<br>
> You still have to run `sudo port test` explicitly to run tests.<br>
><br>
>> Does that change where the output is sent?<br>
><br>
> No. I'm not aware of a proper method to do this, either. You might be<br>
> able to fiddle with MacPorts' internal verbosity setting, but that<br>
> would be a hack.<br>
><br>
> --<br>
> Clemens Lang<br>
<br>
</span>Is the test phase for debugging?<br>
<br>
This script tests each math package in a CAS program after build. Would it would make more sense to keep this as a variant and the script at post-build?<br>
<span class="HOEnZb"><font color="#888888"><br>
Mark<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
macports-dev mailing list<br>
<a href="mailto:macports-dev@lists.macosforge.org">macports-dev@lists.macosforge.org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-dev" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-dev</a><br>
</div></div></blockquote></div><br></div>