Rackunit could probably provide some kind of summary information for these top-level tests that could then be queried (via an extra call that a rackunit programmer puts at the end of the last test file) to determine how to exit. <div> <br></div><div>I know that I wish there were some kind of summary "you passed N tests" instead of silence when nothing fails.</div><div><br></div><div>Robby<br><br>On Wednesday, March 20, 2013, Diogo F. S. Ramos wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jay McCarthy <<a href="javascript:;" onclick="_e(event, 'cvml', 'jay.mccarthy@gmail.com')">jay.mccarthy@gmail.com</a>> writes:<br> <br> > On Wed, Mar 20, 2013 at 1:25 PM, Diogo F. S. Ramos <<a href="javascript:;" onclick="_e(event, 'cvml', 'diogofsr@gmail.com')">diogofsr@gmail.com</a>> wrote:<br> >> My backup plan is to write a filter that will wrap around `raco test<br> >> ...'. It will then output everything `raco test ...' outputs but will<br> >> heuristically look for failures, like the word "FAILURE" or the phrase<br> >> "Check failure", returning non-0 values accordingly.<br> ><br> > Another option is to just look for output to STDERR. That's what DrDr<br> > does to be testing system agnostic (in addition to looking for non-0<br> > exit codes.)<br> <br> Uh, great idea. Thank you.<br> ____________________<br> Racket Users list:<br> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> </blockquote></div>