Thank you, Alex, this seems to have just the right set of information. I'm curious why you use `foldts-test-suite` instead of `fold-test-results`, whose documentation says "Hence it should be used in preference to foldts-test-suite <https://docs.racket-lang.org/rackunit/internals.html?q=foldts-test-suite#%28def._%28%28lib._rackunit%2Fmain..rkt%29._foldts-test-suite%29%29>." (And while David's points about the verbosity are well taken, my TAs are likely to be used to the rackunit primitives, though I think I'll consider borrowing some of his aliases for shorter testing primitive names.)
In the success case, the result seems to be `void` (rather than, say, a value corresponding to the type of test). Are there cases where it's not void? In the failure case, is there a procedure to convert the `exn:test:check` value into a human-readable string? I'm guessing you have some serialization process for the XML test report. Sadly, errors during test execution aren't sandboxed, so if there's an error in a test, the whole suite breaks down. I think this means I'm going to have to write custom testing procedures anyway. Shriram -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAJUf2yR7gxTQ1ZLfakM2LTCJevLhaabifbia%2BEuCo4ApzayMAA%40mail.gmail.com.