Debian Bug report logs - #971507
uget: autopkgtest must be marked superficial

Package: src:uget; Maintainer for src:uget is Elías Alejandro Año Mendoza <[email protected]>;

Reported by: Sudip Mukherjee <[email protected]>

Date: Wed, 30 Sep 2020 21:12:12 UTC

Severity: important

Reply or subscribe to this bug.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to [email protected], Elías Alejandro Año Mendoza <[email protected]>:
Bug#971507; Package src:uget. (Wed, 30 Sep 2020 21:12:14 GMT) (full text, mbox, link).


Acknowledgement sent to Sudip Mukherjee <[email protected]>:
New Bug report received and forwarded. Copy sent to [email protected], Elías Alejandro Año Mendoza <[email protected]>. (Wed, 30 Sep 2020 21:12:14 GMT) (full text, mbox, link).


Message #5 received at [email protected] (full text, mbox, reply):

From: Sudip Mukherjee <[email protected]>
To: [email protected]
Subject: uget: autopkgtest must be marked superficial
Date: Wed, 30 Sep 2020 22:10:08 +0100
Source: uget
Severity: important
Usertags: superficialtest
X-Debbugs-CC: [email protected]

Dear Maintainer,

It has been noticed that the autopkgtest in uget is running a
trivial command that does not provide significant test coverage:

	- testcommand: uget-gtk --version

Executing that command is considered to be a trivial test, which
does not provide significant coverage for a package as a whole.
But these tests are a useful way to detect regressions in dependencies
and prevent them from breaking your package.

However, it is important that we are realistic about the level of
test coverage provided by these commands: most regressions cannot be
detected in this way. So it is not appropriate for packages with only
superficial tests to have the reduced migration time to migrate from
unstable to testing as that means less opportunity for testing by users
compared to the package with no tests.

To support this, the keyword "Restrictions: superficial" has been
defined [1]. Packages where all tests are marked with this keyword are not
considered for the reduced migration age from unstable to testing, and
will not be allowed to migrate automatically in later stages of the
freeze [2].

Its always better to have more extensive testing than having
superficial testing, which again is better than having no test.

Please consider i) Adding a non-trivial test, and/or ii) Mark the
trivial test with "Restrictions: superficial", similar to
[3] or [4].

The Release Team has listed this issue in the list of Release Critical
Issues for bullseye [5] and has mentioned that the test must be marked
superficial if it is not testing one of its own installed binary
packages in some way. As a result, the severity of this bug report might
be increased to serious in future.

[1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions
[2] https://release.debian.org/bullseye/freeze_policy.html
[3] https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468
[4] https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3
[5] https://release.debian.org/bullseye/rc_policy.txt


--
Regards
Sudip




Send a report that this bug log contains spam.


Debian bug tracking system administrator <[email protected]>. Last modified: Tue May 13 14:54:24 2025; Machine Name: bembo

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU General Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.