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

Groups > linux.debian.maint.python > #14870 > unrolled thread

Re: python3-openid: autopkgtest must be marked superficial

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: python3-openid: autopkgtest must be marked superficial Malik Mlitat <mlitat88@googlemail.com> - 2023-01-29 13:10 +0100

#14870 — Re: python3-openid: autopkgtest must be marked superficial

Hello DPTeam,

I updated python3-openid [1] to close #974502 and I need a maintainer to 
upload it.

[1] https://salsa.debian.org/python-team/packages/python3-openid

Regards,

Malik


On Wed, 11 Nov 2020 10:05:54 -0800 (PST) Sudip Mukherjee 
<sudipm.mukherjee@gmail.com> wrote:

 > Source: python3-openid
 > X-Debbugs-CC: elbrus@debian.org
 > Severity: important
 > Usertags: superficialtest
 >
 > Dear Maintainer,
 >
 > It has been noticed that the autopkgtest in python3-openid is running a
 > trivial command that does not provide significant test coverage:
 >
 > - python3 -c "import openid; print(openid)"
 >
 > 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
 >
 >

[toc] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web