Path: csiph.com!1.us.feeder.erje.net!3.us.feeder.erje.net!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!usenet.goja.nl.eu.org!aioe.org!bofh.it!news.nic.it!robomod
From: Simon McVittie <smcv@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: pybuild-autopkgtest (was: Notes from the DC22 Python Team BoF)
Date: Wed, 27 Jul 2022 18:50:01 +0200
Message-ID: <ENSop-ecZI-3@gated-at.bofh.it>
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>
X-Original-To: debian-python@lists.debian.org
X-Mailbox-Line: From debian-python-request@lists.debian.org  Wed Jul 27 16:46:40 2022
Old-Return-Path: <smcv@debian.org>
X-Amavis-Spam-Status: No, score=-107.833 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.714, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: smcv
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/20127
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/YuFr35Hsh0ZJiKNv@momentum.pseudorandom.co.uk
Approved: robomod@news.nic.it
Lines: 15
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Wed, 27 Jul 2022 17:46:23 +0100
X-Original-Message-ID: <YuFr35Hsh0ZJiKNv@momentum.pseudorandom.co.uk>
X-Original-References: <f115f75a-29b9-c5ce-fad8-eee517078724@debian.org> <Yt5Oi1Z1XT2WBq8H@d-and-j.net> <Yt//K7KcYBPGhvqk@debian.org> <YuD04oxQlwPQ2myH@d-and-j.net>
Xref: csiph.com linux.debian.maint.python:14293

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