Re: running tests against installed version of package
> ... little cheat: run the tests after install:
> https://sources.debian.net/src/pytest-catchlog/1.2.2-1/debian/rules/
Ok, thanks for that.
In my case I found the order is not important. What is important is that
the tests are run via "setup.py" which will write/read the
APScheduler.egg-info/*
--- cut ---
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_test
I: pybuild base:184: cd /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest tests
============================= test session starts ==============================
platform linux2 -- Python 2.7.11+, pytest-2.9.1, py-1.4.31, pluggy-0.3.1
rootdir: /<<PKGBUILDDIR>>, inifile: setup.cfg
collected 401 items
...
--- cut ---
vs
--- cut ---
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
I: pybuild base:184: python2.7 setup.py test
running test
running egg_info
writing requirements to APScheduler.egg-info/requires.txt
writing APScheduler.egg-info/PKG-INFO
writing top-level names to APScheduler.egg-info/top_level.txt
writing dependency_links to APScheduler.egg-info/dependency_links.txt
writing entry points to APScheduler.egg-info/entry_points.txt
reading manifest file 'APScheduler.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'APScheduler.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform linux2 -- Python 2.7.11+, pytest-2.9.1, py-1.4.31, pluggy-0.3.1
rootdir: /<<PKGBUILDDIR>>, inifile: setup.cfg
collected 401 items
--- cut ---
--
Brian May <brian@linuxpenguins.xyz>
https://linuxpenguins.xyz/brian/
Reply to: