<div dir="ltr">I didn't mean to suggest obligatory output.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 7:07 PM, Diogo F. S. Ramos <span dir="ltr"><<a href="mailto:diogofsr@gmail.com" target="_blank">diogofsr@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Jay McCarthy <<a href="mailto:jay.mccarthy@gmail.com">jay.mccarthy@gmail.com</a>> writes:<br> <br> > I think that would be a great solution. We could also put that call<br> > into 'taco test' with an optional switch or as the default if it were<br> > popular and/or not rackunit-specific<br> ><br> > Jay<br> ><br> > On Wednesday, March 20, 2013, Robby Findler wrote:<br> ><br> > Rackunit could probably provide some kind of summary information<br> > for these top-level tests that could then be queried (via an extra<br> > call that a rackunit programmer puts at the end of the last test<br> > file) to determine how to exit.<br> ><br> ><br> > I know that I wish there were some kind of summary "you passed N<br> > tests" instead of silence when nothing fails.<br> <br> </div>I don't know if I'm understanding you correctly, but it's a normal<br> behavior for tools to be silent if everything went OK.<br> <br> Adding some obligatory output seems to make the life harder for those<br> who want to use `raco test' as a tool.<br> </blockquote></div><br></div>