Well probably check-equal?, check-match, check-pred, check, and check-exn would be the main ones, with check-equal? probably being the most important, but what would be really cool would be something that could generalize over all rackunit checks, so that even checks defined with define-check, define-simple-check, and define-binary-check will work. Maybe some of these could help?: http://docs.racket-lang.org/rackunit/internals.html http://docs.racket-lang.org/rackunit/internals.html#%28part._.Functions_to_.Run_.Tests%29
On Apr 26, 2015, at 7:44 PM, Mira Leung <emailmirale...@gmail.com> wrote: > On Sunday, April 26, 2015 at 6:18:41 AM UTC-7, Alex Knauth wrote: >> Wow this is awesome! >> Can you get to support rackunit too? > > > Thanks Alex. Which rackunit test variants would you prioritize? > > -- > 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. > For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
