[racket-dev] testing

From: Carl Eastlund (cce at ccs.neu.edu)
Date: Thu Aug 4 12:17:13 EDT 2011

On Thu, Aug 4, 2011 at 12:11 PM, Matthias Felleisen
<matthias at ccs.neu.edu> wrote:
> One of the responses to the draft of the Racket style guide contains the following paragraph:
>> There should be unified way to test collections. Let's say I fix
>> something in collect `foo', there should be an obvious way to run
>> `foo''s tests. Currently, the closest we have would be to look in
>> `tests/foo', and see if anything looks like an entry point.
>> Standardizing on test suite entry points would make it easier for
>> people to run tests after fixing bugs in collects that are not their
>> own. Such an entry point could be that each collect `X' is required to
>> have a `tests/X/run.rkt' file that, when run, runs the test suite for
>> `X'.
> I don't consider this topic appropriate for the style guide.

Why not?

> But I consider it important enough to bring up for discussion.
> QQQ: Is there a policy that spells out testing collections?
> QQQ: Should we try to formulate one or leave individual testing styles alone?

We need to standardize on something.  It is necessary to run other
people's tests too often to rely on this search-and-hope method.  Even
a README convention so that each collection spells out how to test it
would be a start in the right direction.


Posted on the dev mailing list.