This page discusses how autopkgtest fits in to Debian's continuous integration framework. To learn how to use autopkgtest, see autopkgtest. For recommendations about good tests, see best practices. For information about Debian's continuous integration framework, see ContinuousIntegration.
Packages uploaded to Debian are continuously tested by the debci package. For details, see the Debian CI service and the graphs of checks over time.
![/!\](/htdocs/debwiki/img/alert.png "/!\"){kind=small}
"autopkgtest" is the name of a package, "an autopkgtest" is the name for a test suite managed by by that package
Contents
Usage
If a test fails on ci.debian.net, you will probably want to run it locally to debug it.
Find the package's page on the site - for example, here is the page for gdk-pixbuf. Note that each test is associated with a release (e.g. unstable) and an architecture (e.g. amd64). If only one release or architecture is failing, you will probably need to use that release or architecture for your local tests.
Follow the instructions to run tests for your package, making sure to specify release and architecture if necessary.
autopkgtest runs tests located in debian/tests - check files in that directory for more information.
Still can't reproduce issues?
The Debian CI service environment may be subtly different from your environment. You can request access to the container that ran the tests by pinging elbrus or terceiro on #debci.
See also
Debian LTS Team - autopkgtest: extensive documentation on running autopkgtest manually with different isolation modes
Tips for autopkgtest in Debian: overcoming several setup issues and some advice related to lxc and apt-cacher-ng