From: Intransition <transfire@...>
Date: 2010-04-22T05:04:04+09:00
Subject: Re: Proposing a Ruby Packaging Standard



On Apr 21, 2:50 pm, Luis Lavena <luislav...@gmail.com> wrote:
> On Apr 21, 2:07 pm, Damian Janowski <damian.janow...@gmail.com> wrote:
>
> > [...]
>
> > Under Tests, should there be a standard for running the entire test
> > suite? Say, `rake`?
>
> That would trigger other dependencies developers might have in their
> rake tasks (like coverage, documentation, mutation testing, etc.)
>
> I simple "ruby -Ilib test/test*.rb" should suffice, right?

Depends on the testing framework. Some do not support autorun. Some
tests aren't located in test/. For most 'rake test' is the common
practice, but as someone who does not use rake I have at times
wondered how best to approach this myself. It's not a huge issue
really, since only developers tend to actually run the tests and
whatever system used it's not too hard for developers to figure out.
On occasion though I have provided a ruby executable called 'script/
test' to handle it.