Hi Ben,
> Cédric Boutillier <cedric.boutillier@gmail.com> writes:
> > A best practice instaured in the Ruby Extras Team is to run the test
> > suite at build time to ensure that it will work with the versions of
> > the Ruby interpreter supported by Debian.
> Where is that documented? I couldn't find it at
> <URL:http://wiki.debian.org/Teams/Ruby/Packaging>.
That is _very_ briefly mentionned on this page as one item in the
description of gem2deb, the packaging tool we are using.
gem2deb is a replacement for our current cdbs-based packaging suite. It:
[...]
* runs the test suite as part of the build, for each ruby
implementation (yes, it's possible to override this)
There is some more information in dh_ruby(1), in the gem2deb package.
> Instead, disable the tests which require that, since they are not unit
> tests and hence are irrelevant to the goal of testing the code against
> the Ruby interpreter.
The package is meant to interact with a mysqld server, so the test suite
provided by upstream contains mainly (if not only) tests requiring a
working instance of mysqld somewhere. Except running a syntax check,
that is the only thing I can do to test automatically if the software
works or not with the Ruby interpreters and other Ruby libraries we have
in Debian.
I must admit that it is very helpful to have some pieces of code to test
the software we are packaging, as it is very easy to forget a
dependency (most of the time, there is no compilation, so missing
libraries are detected at runtime).
Cédric
Attachment:
signature.asc
Description: Digital signature