Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #8194

Test suite needs script built after dh_auto_test is run

From Sean Whitton <spwhitton@spwhitton.name>
Newsgroups linux.debian.maint.python, linux.debian.devel.mentors
Subject Test suite needs script built after dh_auto_test is run
Date 2016-02-05 05:10 +0100
Message-ID <qYFSz-3zj-19@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hello,

I'm packaging a Python application, ocrmypdf [1], that has a test suite
run by py.test.  Most of the tests fail because they try to call the
/usr/bin/ocrmypdf script.  This script doesn't exist until after
debhelper has run setup.py, which generates it using its "entry points
script" feature.  And this comes after dh_auto_test.

The only solution I've come up with is producing my own entry point
script and putting it into $PATH for the test suite to use.  But that
rather defeats the purpose of testing the actual package's contents.

What would be the most elegant way to handle this?  Can anyone point me
to a package that had a similar issue with the test suite needing a file
not yet generated?

Thanks.

[1] https://github.com/jbarlow83/OCRmyPDF

-- 
Sean Whitton

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Test suite needs script built after dh_auto_test is run Sean Whitton <spwhitton@spwhitton.name> - 2016-02-05 05:10 +0100
  Re: Test suite needs script built after dh_auto_test is run Barry Warsaw <barry@python.org> - 2016-02-05 20:20 +0100
    Re: Test suite needs script built after dh_auto_test is run Sean Whitton <spwhitton@spwhitton.name> - 2016-02-07 00:20 +0100

csiph-web