The idea for this session it to get together and discuss all
autopkgtest/Debian CI related aspects. If you have ideas on how to test
your package but don’t know exactly how to wire things up for running
with autopkgtest, want to share your joy and/or your frustration with
the tools or with the environments, or have tips or questions on writing
autopkgtest tests, this is for you.
autopkgtest runs tests on binary packages. The tests are run on the
package as installed on a testbed system (which may be found via a
virtualization or containment system). The tests are expected to be
supplied in the corresponding Debian source package. See autopkgtest(1)
and /usr/share/doc/autopkgtest. Depending on which virtualization server
you want to use, you need to install additional packages (schroot, lxc,
lxd, or qemu-system)
The migration software used by the Release Team (called britney) uses
the results from autopkgtest of a package and it's reverse dependencies
to determine if a package is ready to migrate to testing. A regression
in any of these scheduled tests will block migration.
Debian CI ([ci.debian.net](https://ci.debian.net "ci.debian.net")) runs autopkgtest against the entire Debian archive, Adding autopkgtest tests to your package will automatically make those tests run on Debian CI as soon as the package hits the archive.
Salsa CI ([salsa.debian.org](https://salsa.debian.org]) can be used to run tests the moment changes are pushed to packaging archives hosted on that server.