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. > > Robby > > On Wednesday, March 20, 2013, Diogo F. S. Ramos wrote: > >> Jay McCarthy <[email protected]> writes: >> >> > On Wed, Mar 20, 2013 at 1:25 PM, Diogo F. S. Ramos <[email protected]> >> wrote: >> >> My backup plan is to write a filter that will wrap around `raco test >> >> ...'. It will then output everything `raco test ...' outputs but will >> >> heuristically look for failures, like the word "FAILURE" or the phrase >> >> "Check failure", returning non-0 values accordingly. >> > >> > Another option is to just look for output to STDERR. That's what DrDr >> > does to be testing system agnostic (in addition to looking for non-0 >> > exit codes.) >> >> Uh, great idea. Thank you. >> ____________________ >> Racket Users list: >> http://lists.racket-lang.org/users >> > -- Jay McCarthy <[email protected]> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93
____________________ Racket Users list: http://lists.racket-lang.org/users
