I didn't mean to suggest obligatory output.
On Wed, Mar 20, 2013 at 7:07 PM, Diogo F. S. Ramos <[email protected]>wrote: > Jay McCarthy <[email protected]> writes: > > > I think that would be a great solution. We could also put that call > > into 'taco test' with an optional switch or as the default if it were > > popular and/or not rackunit-specific > > > > Jay > > > > On Wednesday, March 20, 2013, Robby Findler wrote: > > > > 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. > > > > > > I know that I wish there were some kind of summary "you passed N > > tests" instead of silence when nothing fails. > > I don't know if I'm understanding you correctly, but it's a normal > behavior for tools to be silent if everything went OK. > > Adding some obligatory output seems to make the life harder for those > who want to use `raco test' as a tool. >
____________________ Racket Users list: http://lists.racket-lang.org/users
