<div dir="ltr">I think that currently you can look at what drdr does. That's the best we have.<div><br></div><div>Meanwhile, I think that if you are willing to live a bit on the edge, you can try to run some reasonable looking tests (break something intentionally and make sure they complain, say) and then go ahead and push and let drdr sort things out more. Worst comes to worst, you just revert a commit and try again tomorrow, no? </div>
<div><br></div><div style>Robby</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 27, 2013 at 1:54 PM, Danny Yoo <span dir="ltr"><<a href="mailto:dyoo@hashcollision.org" target="_blank">dyoo@hashcollision.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Feb 27, 2013 at 7:01 AM, Jay McCarthy <<a href="mailto:jay.mccarthy@gmail.com">jay.mccarthy@gmail.com</a>> wrote:<br>
> The tests are run by running "main.rkt", which has no rerrors when you<br>
> run it. It is a bit strange that those errors happen when run that<br>
> way, but I think it just means that "eval" should control the context<br>
> of the sub-programs more.<br>
<br>
<br>
Ok.<br>
<br>
Is there anything that can be done to regularize how all the<br>
collections in Racket are to be tested? It doesn't have to be as<br>
strict as forcing use of rackunit or eli-tester: just having a<br>
convention like "Run the test-all.rkt at the toplevel of a collection<br>
to run all its tests" would be a major improvement.<br>
<br>
At the moment, each collection follows its own rules for testing it.<br>
The non-uniform structure of the testing infrastructure makes it<br>
difficult to develop and maintain Racket's libraries. I can make a<br>
bug fix, but without a fixed point of entry to test the changes I've<br>
made, I get nervous: maybe I'm running all the tests for this<br>
collection, but maybe I've missed something.<br>
<br>
I had assumed that all of Racket's automated test suite would be<br>
driven by collects/tests/run-automated-tests.rkt, but it only runs<br>
some of the core Racket tests: it doesn't hit the entire collects<br>
tree. In absence of that, I thought raco test was the way to go, but<br>
that doesn't currently work either.<br>
_________________________<br>
Racket Developers list:<br>
<a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
</blockquote></div><br></div>