Never mind. I figured it out. Makefile is smart enough to just stop and break if a non-zero return code is encountered by any shell call. So, all I need to do is have my unit test return non-zero if an exception is caught.<br>
<br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p>I am setting up my unit test for a new COIN project to run
when 'make test' is run. How do folks deal with test failures? My code catches
exceptions and throws an error to the screen - but the test just proceeds from
that point. In fact, my first test might fail then the next few pass - and the
only indication of the failure is if the user looks for the phrase "COIN
Exception" in the make log. How do folks usually deal with this so that
failed tests don't go un-noticed?</p><br></div></div></blockquote></div>