autopkgtest

Build the package in the current directory and run all tests directly on the system

$ autopkgtest -- [null]

$ autopkgtest --test-name=[test_name] -- [null]

$ autopkgtest [package] -- [null]

$ autopkgtest -- [chroot] [path/to/new_root]

$ autopkgtest [[-B|--no-built-binaries]] -- [null]

autopkgtest [options] [--] package.dsc|package.deb [=version] [testname [args...]]

-h, --help
    Show help message and exit

--version
    Print version information

-d, --debug
    Enable debug output

-q, --quiet
    Reduce output verbosity

-v, --verbose
    Increase output verbosity

--shell-fail
    Fail if shell command returns non-zero

--timeout=SECONDS
    Abort test after timeout

--apt-pocket=POCKET
    Add PPA-like pocket to apt sources

--apt-upgrade
    Upgrade packages before testing

--setup-commands=CMD
    Run commands before test setup

--env=VAR=VALUE
    Set environment variable in testbed

--ssh=HOSTNAME
    Use SSH testbed (user@host)

--qemu=/path/to/image
    Use QEMU VM testbed

--lxd
    Use LXD container testbed

--chroot=/path/to/chroot
    Use local chroot testbed

--null
    Null testbed (dry-run simulation)

-s, --source=SOURCE
    Path to source package directory

--build-deps=...
    Build-dependency inclusion list

--no-build-deps
    Skip building from source

--testbed-overlay=DIR
    Overlay directory for testbed

--allow-stderr
    Passed to tests allowing stderr

--immediate
    Run tests immediately without setup

--schedule
    Output schedule for queueing

autopkgtest is a versatile tool for running automatic tests on Debian and Ubuntu packages. It executes tests defined in the debian/tests directory of source packages or associated with binary packages. Tests can run in diverse environments like chroots, LXD containers, QEMU VMs, SSH hosts, or physical machines, simulating various deployment scenarios.

It supports .dsc source packages, binary .deb/.udeb/.ipk files, and integrates with CI systems such as Debian's ci.debian.net or Ubuntu's autopkgtest cloud. Tests are declared via simple control files specifying dependencies, restrictions (e.g., <allow-stderr>), and actions (e.g., apt install). autopkgtest handles package installation, dependency resolution via apt, and reports pass/fail outcomes with logs.

Common uses include developer testing during build cycles, release team validation, and migration testing between suites. It ensures packages work correctly post-install, under resource limits, and in isolation, catching regressions early.

Requires debian/tests/control files in packages; testbeds like schroot/LXD must be pre-configured; resource-intensive for VMs; network access limited by default; fails if dependencies unmet.

Tests defined in debian/tests/control: Tests: test1 test2
Restrictions: needs-root, allow-stderr
Depends: @, @builddeps@

Supports AWS/GCE/Azure via autopkgtest-cloud; used in Ubuntu Proposer for migration testing.

Produces .log, .html reports; exit codes: 0=pass, 2=fail, 4=setup-fail, 8=internal-error.

Originated as Debian's autopkgtest (formerly 'adt-run') around 2011 for QA automation, replacing older piuparts. Merged into autopkgtest project in 2013; actively maintained by Debian/Ubuntu Release Teams for CI/CD pipelines like ci.debian.net. Supports modern testbeds since Ubuntu 14.04+.

schroot(1), lxd(1), qemu(1), debuild(1), piuparts(1), dpkg-buildpackage(1)