raco test's job is to run the 'test' modules of the programs listed. It imposes no obligations on what these test modules do and does not communicate with them in any way. Thus, it has no concept of "a check failing".
If you want, you can write your test modules so that they exit with non-0 when they fail, which raco test will pass on to you: (module+ test (unless (= 0 (f 5)) (error 'test-failure "F of 5 is not 0!"))) If this is your test module, then raco test will return a non-0 because 'error' returns a non-0. There's a good reason that 'rackunit' doesn't work this way, but if you disagree with that design, you could use a different testing system and 'raco test' would respect it. Jay On Wed, Mar 20, 2013 at 10:40 AM, Diogo F. S. Ramos <[email protected]> wrote: > `raco test ...' seems to return 0 whenever a test fails or not. > > Is it possible to make it return non 0 values if a check fails? > ____________________ > 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
