Thanks to Matthias, John, and Greg for their suggestions! I explored
the raco documentation in more detail and I will try to come up with
some good solution. My main goal is to have convenient modes of operation:

1) Developers (currently me) should be able to run easily the
   subset of tests that is relevant for their current work.

2) Users and occasional contributors should be able to run easily
   the entire test suite of my collection/library.

Matthias Felleisen writes:

 > Use different names for the various test modules. 
 > At the local level, you can use module+ test. For
 > the integration tests, you may wish to use module+
 > integration.

Given that I frequently split modules as my code base grows,
I'd like to avoid having integration tests in any one module,
and prefer a specific module for the tests (that doesn't change).
However, it just occurred to me that nothing prevents me from
having a module that is empty except for a test submodule.
I'll see if that works for me.


John Clements writes:

 > The ‘raco test’ tool can be applied to a collection, using the
 > “—collection” (or simply “-c”) flag. You can see a full list of the
 > available flags by running
 > 
 > raco help test

True, but it isn't terribly clear what "interpreting arguments as
collections" means. The Racket documentation is a bit more precise in
saying that a collection is treated like a dictionary containing
modules, so it's just another way to specify a directory path.


Greg Hendershott writes:

 > I did `raco help test` just now and discovered even more options than
 > I remembered. Including fun things like running tests in parallel,
 > printing a summary table, and so on.

It's indeed quite feature-rich.

 > racket-mode has a couple features related to tests and coverage. They
 > currently assume the module is `test`. That's been sufficient for me
 > so far, and I handle more "exotic" test things in a Makefile. But feel

I think it will be sufficient for me as well. In racket-mode, I mainly
want to run one module's unit tests. If I can integrate them into
a global test-running scheme with raco, that's all I expect to need.


Konrad

-- 
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.

Reply via email to