Are you using emacs racket-mode? I have experience this issue only in that mode since it does not (to my knowledge) implement all the error anchoring features of DrRacket. If you run in DrRacket the errors and contract violations should be highlighted as in the screengrab below. Best, Tom
On Tue, Apr 2, 2019 at 3:41 PM zeRusski <vladilen.ko...@gmail.com> wrote: > I am a big fan of having tests alongside code so (module+ test ...) is > magic. The only annoyance I've been running into lately is error reporting. > If I have many test chunks spread around my code and some code change > throws an exception or a contract violation it is impossible to tell which > test triggered it. The only thing in the context is (submod "file.rkt" > test):1:1. On occasion you get the exact point the exception happened but > again no context, so no way to figure which check specifically ran the > buggy code. Normally I would go through a dance of bisecting to pinpoint > the culprit, but now that I have many tests its become a major pain. Is > there a better way? > > Thanks > > -- > 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.
