[racket-users] best practice for drdr + interactive tests

I have tests that are timing out in drdr (mred-extensions.rkt) because they’re graphical tests that open a window and expect the user to inspect and close it. I don’t expect these tests to be run by drdr, but I don’t want to delete them. I can see the following choices: - Use info.rkt to

Re: [racket-users] best practice for drdr + interactive tests

Changing `test` to `main` sounds best to me. At Wed, 28 Oct 2015 13:27:13 -0400, "'John Clements' via Racket Users" wrote: > I have tests that are timing out in drdr (mred-extensions.rkt) because > they’re > graphical tests that open a window and expect the user to inspect and close > it. I