Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14293
| From | Simon McVittie <smcv@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) |
| Date | 2022-07-27 18:50 +0200 |
| Message-ID | <ENSop-ecZI-3@gated-at.bofh.it> (permalink) |
| References | <EMrzX-dlxq-1@gated-at.bofh.it> <EN1k5-dHa4-1@gated-at.bofh.it> <ENucp-dYnS-3@gated-at.bofh.it> <ENKqS-e8mT-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, 27 Jul 2022 at 09:18:42 +0100, Julian Gilbey wrote:
> There seems to be little point running both pybuild-autopkgtest and a
> manually written debian/tests/* test suite.
I think it can make sense to have both. d/tests is the right place for
an integration test that checks things like "any user-facing executables
are correctly in the PATH", which an upstream-oriented test probably
cannot assert because you might be installing into ~/.local or similar.
Using src:tap.py as an example, pybuild-autopkgtest should presumably
replace d/tests/python3 and/or d/tests/python3-with-recommends (which
are tests for the library you get from "import tap"), but wouldn't test
the tappy(1) CLI entry point, which is tested by d/tests/tappy.
smcv
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Notes from the DC22 Python Team BoF Louis-Philippe Véronneau <pollo@debian.org> - 2022-07-23 20:00 +0200
Re: Notes from the DC22 Python Team BoF Julian Gilbey <julian@d-and-j.net> - 2022-07-25 09:40 +0200
Re: Notes from the DC22 Python Team BoF Thomas Goirand <zigo@debian.org> - 2022-07-27 10:00 +0200
Re: Notes from the DC22 Python Team BoF Louis-Philippe Véronneau <pollo@debian.org> - 2022-07-27 16:20 +0200
pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Julian Gilbey <julian@d-and-j.net> - 2022-07-25 10:10 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Antonio Terceiro <terceiro@debian.org> - 2022-07-26 17:00 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Scott Kitterman <debian@kitterman.com> - 2022-07-26 17:50 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Antonio Terceiro <terceiro@debian.org> - 2022-07-26 23:00 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Paul Wise <pabs@debian.org> - 2022-07-27 02:20 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Louis-Philippe Véronneau <pollo@debian.org> - 2022-07-27 05:50 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Julian Gilbey <julian@d-and-j.net> - 2022-07-27 10:20 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Louis-Philippe Véronneau <pollo@debian.org> - 2022-07-27 16:30 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Julian Gilbey <julian@d-and-j.net> - 2022-07-27 20:50 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Julian Gilbey <julian@d-and-j.net> - 2022-07-27 22:40 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Julian Gilbey <julian@d-and-j.net> - 2022-07-28 20:50 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Louis-Philippe Véronneau <pollo@debian.org> - 2022-08-18 02:00 +0200
Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF) Simon McVittie <smcv@debian.org> - 2022-07-27 18:50 +0200
csiph-web