On 2007-01-11, Nathaniel Talbott <ntalbott / gmail.com> wrote:

> I'd much rather not have to manually go through each gem, figure out
> what it needs so that I can run its tests, store that somehow (since
> it's not in the spec), install the dependencies since they aren't
> already, and all that to just automatically run tests for the gems.

Maybe a simple convention is all that's needed.  (Echoing myself in
another thread.)  If the full test set for "foo" is too cumbersome,
release it as "foo-test".  It should be easy to write a script that
installs "foo-test" for every installed gem "foo".

(Actually I think that the test-driven philosophy should encourage
developers to think of the tests as just part of the product and
package them as such whenever it is reasonably possible.  But there
are bound to be occasions when this is not practical.)

Jeremy Henty