Raco test runs the file if there is not test sub module. Fwiw. <span></span><br><br>On Saturday, July 6, 2013, Eli Barzilay wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It doesn't make much sense to use a test submodule in files that are<br>
intended to be (only) tests.<br>
<br>
<br>
Earlier today, Robby Findler wrote:<br>
> That's the plan. Thanks for fixing them.<br>
><br>
> Robby<br>
><br>
><br>
> On Sat, Jul 6, 2013 at 8:47 AM, Sam Tobin-Hochstadt <<a href="javascript:;" onclick="_e(event, 'cvml', 'samth@ccs.neu.edu')">samth@ccs.neu.edu</a>> wrote:<br>
><br>
> I recently discovered that DrDr runs `raco test` by default on files,<br>
> and has since February. However, the DrDr documentation says that it<br>
> runs `racket -t`. I discovered this because the change caused many of<br>
> the `net` tests to no longer actually run; see<br>
><br>
> <a href="http://drdr.racket-lang.org/27042/pkgs/racket-pkgs/racket-test/tests/" target="_blank">http://drdr.racket-lang.org/27042/pkgs/racket-pkgs/racket-test/tests/</a><br>
> net/url.rkt<br>
><br>
> which appears to be successful, even though running `racket` on that<br>
> file would have shown the error that I fixed in<br>
> <a href="https://github.com/plt/racket/commit/a4e529a816" target="_blank">https://github.com/plt/racket/commit/a4e529a816</a> . These tests are a<br>
> particularly bad case because they run all their tests in the `main`<br>
> submodule, and thus are *not* executed by `raco test`. If the plan is<br>
> for everything to run with `raco test`, I'll fix these tests. But<br>
> what is the plan?<br>
<br>
--<br>
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:<br>
<a href="http://barzilay.org/" target="_blank">http://barzilay.org/</a> Maze is Life!<br>
</blockquote>