[DRE-maint] Bug#958019: Please add option to specify the test file to run
Antonio Terceiro
terceiro at debian.org
Mon Apr 20 14:34:29 BST 2020
On Fri, Apr 17, 2020 at 03:10:18PM +0200, Daniel Leidert wrote:
> Package: gem2deb-test-runner
> Version: 1.0.5+b1
> Severity: wishlist
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> The use case I have is ruby-rubocop-performance. It cannot run the tests
> during build because rubocop already build-depends on it. Because
> ruby-rubocop-performance would require rubocop this would create a circular
> build-depndency. The solution to this probably is to run the tests in
> autopkgtest only but prevent the tests from running during build. However
> gem2deb-test-runner relies on a specific set of test files (e.g.
> debian/ruby-tests.rake) and if they are there, the will be run during build too
> ... exactly what we need to prevent. So it would be nice I could provide a test
> file to the gem2deb-test-runner command in the autopkgtest control file.
This would require you to have an explicit debian/tests/control, and
then not gaining any updates done in autodep8.
Most gem2deb-test-runner test files are made of arbitrary ruby code; you
can just check for autopkgtest and bail out otherwise. Example:
https://sources.debian.org/src/ruby-concurrent/1.1.6+dfsg-3/debian/ruby-tests.rake
Maybe we could document this explicitly in the manpage.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20200420/b67f1a18/attachment.sig>
More information about the Pkg-ruby-extras-maintainers
mailing list