[3dprinter-general] Bug#974499: libsavitar: autopkgtest must be marked superficial
sudipm.mukherjee at gmail.com
Wed Nov 11 18:05:50 GMT 2020
X-Debbugs-CC: elbrus at debian.org
It has been noticed that the autopkgtest in libsavitar is running a
trivial command that does not provide significant test coverage:
- $py -c "import Savitar; print(Savitar)"
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 . 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
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
 or .
The Release Team has listed this issue in the list of Release Critical
Issues for bullseye  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.
More information about the 3dprinter-general