In 5.6.30. Testsuite
...
Currently, the only defined value is autopkgtest.
Which is not true, because we have autodep8. Look to: https://anonscm.debian.org/git/lintian/lintian.git/tree/checks/testsuite.pm#n60
And if you want to use autodep8, you need to explicitly add this to d/control.
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 61f2b23..2bc7a07 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -1009,12 +1009,12 @@ reference whose name matches ``refs/dgit/*``. See the manual page of
Simple field containing a comma-separated list of values allowing test
execution environments to discover packages which provide tests.
-Currently, the only defined value is ``autopkgtest``.
-This field is automatically added to Debian source control files by -``dpkg`` when a ``debian/tests/control`` file is present in the source -package. This field may also be used in source package control files if -needed in other situations.
+This field is automatically added to Debian binary control files by +``dpkg``, with the value ``autopkgtest``, when a
+``debian/tests/control`` file is present in the source package. This
+field may also be used in source package control files if needed in
+other situations.
.. _s5.7:
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 61f2b23..2bc7a07 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -1009,12 +1009,12 @@ reference whose name matches ``refs/dgit/*``. See the manual page of
Simple field containing a comma-separated list of values allowing test
execution environments to discover packages which provide tests.
-Currently, the only defined value is ``autopkgtest``.
-This field is automatically added to Debian source control files by -``dpkg`` when a ``debian/tests/control`` file is present in the source -package. This field may also be used in source package control files if -needed in other situations.
+This field is automatically added to Debian binary control files by +``dpkg``, with the value ``autopkgtest``, when a
+``debian/tests/control`` file is present in the source package. This
+field may also be used in source package control files if needed in
+other situations.
.. _s5.7:
Actually, this depends on which autodep8 module you want to use. I know
that my elpa module runs the tests even if the Testsuite: field is
missing, for example.
On Wed, Aug 30, 2017 at 12:56:30PM +0200, Ondrej Novy wrote:
2017-08-26 21:49 GMT+02:00 Sean Whitton <spwhitton@spwhitton.name>:
Actually, this depends on which autodep8 module you want to use. I know that my elpa module runs the tests even if the Testsuite: field is missing, for example.
i think this is true for local build environment only, but not for ci.debian.net. If you want your autodep8 tests to run on Debian CI, you need to explicitly enable them.
Indeed. Alternatively, you need to reach out to the ci.d.n admins: they maintain a manual list of packages for which to run a specific autodep8
thing (which is what has been done for all the things currently in
autodep8 to have them enabled right away for all packages).
2017-08-26 21:49 GMT+02:00 Sean Whitton <spwhitton@spwhitton.name>:
Actually, this depends on which autodep8 module you want to use. I know that my elpa module runs the tests even if the Testsuite: field is
missing, for example.
i think this is true for local build environment only, but not for ci.debian.net. If you want your autodep8 tests to run on Debian CI, you
need to explicitly enable them.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 91:30:55 |
Calls: | 6,658 |
Files: | 12,203 |
Messages: | 5,334,161 |