1 .TH adt\-run 1 2006 autopkgtest "Linux Programmer's Manual"
3 adt\-run \- test an installed binary package using the package's tests
9 .RI [ virt\-server\-arg ...]
13 is the program for invoking the autopkgtest package testing machinery.
15 autopkgtest is a facility for testing binary packages, as installed on
16 a system (such as a testbed system). The tests are those supplied in
19 adt\-run runs each test supplied by a particular package and reports
20 the results. It drives the specified virtualisation regime as
21 appropriate, and parses the test description metadata, and arranges
22 for data to be copied to and from the testbed as required.
24 adt\-run should be invoked (unless options to the contrary are
25 supplied) in the top level directory of the built source tree, on the
26 host. The package should be installed on the testbed.
30 .BR --build-tree [ -tb ] " " \fIdirectory\fR
31 Specifies that the built source tree can be found in
33 (Default: adt-run's current directory, on the host.)
35 .BR --build-source [ -tb ] " " \fIfilename\fR
36 Specifies that the source to use for the tests can be found in
38 (which should be a \fB.dsc\fR). The source will be unpacked
39 and built, and the tests from this build tree will be run.
41 .BR --use-source [ -tb ] " " \fIfilename\fR
42 Specifies that the source to use for the tests can be found in
44 (which should be a \fB.dsc\fR), and that the packages from this
45 build should be the ones tested, and used to satisfy any dependencies;
46 this option is like \fB--build-source\fR and \fB--from-source\fR combined.
48 .BR --user " " \fIusername\fR
49 Specifies that commands on the testbed should generally be run as
50 \fIusername\fR; this option does not make much sense unless the
51 virtualisation environment provides root on the testbed. Commands are
52 run via \fBsu -c\fR; affected commands are tests (other than those
53 which declare that they need root), source package builds and source
54 package binary generation (via fakeroot). If the testbed advertises
55 the \fBroot-on-testbed\fR and \fBsuggest-normal-user=\fR capabilities,
56 the suggested normal is used as the default; otherwise the default is
57 to run commands as the testbed's default user (this can be explicitly
58 requested by specifying the empty string for \fIusername\fR).
60 .BR --fakeroot " " \fIfakeroot-command\fR
61 Specifies that \fBdebian/rules binary\fR should be run via
62 \fIfakeroot-command\fR. The default is \fBfakeroot\fR if the testbed
63 doesn't offer us root or if we are running \fBdebian/rules build\fR as
64 a normal user according to a specified or default value of
65 \fB--user\fR, and no wrapper otherwise.
67 The default is to run without any special
70 Specifies that commands on the testbed should generally be run as
71 \fIusername\fR; this option does not make much sense unless the
72 virtualisation environment provides root on the testbed. Commands
73 are run via \fBsu -c\fR; affected commands are tests (other than those
74 which declare that they need root), source package builds and source
75 package binary generation (except if \fB--fakeroot\fR is specified -
78 Specifies that \fIfilename\fR (which should be a \fB.deb\fR) should be
79 unconditionally installed on the testbed before any tests are run (but
80 after any necessary building). This can be used to test a specific
83 .BR --install-binary [ -tb ] " " \fIfilename\fR
84 Specifies that \fIfilename\fR (which should be a \fB.deb\fR) should be
85 unconditionally installed on the testbed before any tests are run (but
86 after any necessary building). This can be used to test a specific
89 .BR --from-source [ -tb ] " " \fIsource\fR
90 Specifies that \fIsource\fR (which should be a \fB.dsc\fR) should be
91 built on the testbed and then the resulting \fB.deb\fR's
92 used to satisfy dependencies where necessary.
94 .BR --install-from-source [ -tb ] " " \fIsource\fR
95 Specifies that \fIsource\fR (which should be a \fB.dsc\fR) should be
96 built on the testbed and then (some subset of) the \fB.deb\fR's which
97 result should be installed.
99 ;.BR --without-depends | --with-depends-only | --with-depends | --with-recommends
100 ;Specifies dependency handling: These options control whether
101 ;dependencies necessary for building and installing the packages as
102 ;requested will be installed (and possibly deinstalled, if there are
105 ;Each option controls installation of the dependencies for
107 ;.BR --build-source ", " --install-package " and " --install-from-source
108 ;options, until the next dependency handling option; the last
109 ;dependency handling option controls whether dependencies specified in
110 ;the actual test control file are installed.
112 ;The four handling modes are to honour, respectively: no dependencies, only
113 ;\fBDepends\fR, everything except \fBRecommends\fR and \fBSuggests\fR,
114 ;and everything except \fBSuggests\fR.
115 ;The default is \fB--without-depends\fR (it is as if this was
116 ;specified at the start of the command line).
118 ;.BR --package-filter-dependency " [!]\fIpattern\fR[,[!]\fIpattern\fR...]"
119 ;Limits the packages installed (or removed) due to dependencies to
120 ;those matching the specified filter. The filter is a comma-separated
121 ;list of glob patterns (which must match the whole package name); each
122 ;optionally preceded by \fB!\fR (which indicates that matching packages
123 ;should not be installed). The first pattern found determines; if no
124 ;pattern matches, then the package is taken to match the filter iff the
125 ;last pattern had a \fB!\fR.
127 .BR --package-filter-from-source " [!]\fIpattern\fR[,[!]\fIpattern\fR...]"
128 Limits the packages installed directly due to
129 .B --install-from-source
130 directives; the patterns are interpreted as for
131 .BR --package-filter-dependency .
133 .BR --control [ -tb ] " " \fIcontrol\fR
136 should be used as the test control file instead of
137 .B debian/tests/control
138 in the build tree. Note that it is not an error for this file not to
139 exist; that just means that there are no tests.
141 .BR --output-dir [ -tb ] " " \fIoutput-dir\fR
142 Specifies that stderr and stdout from the tests should be placed in
151 .BR log-buildt " (for the build logs from " --build-source ),
153 .RI "(for the build logs from the " i th
154 .BR --install-from-source ),
156 .RI "(for the installation logs from the " j "th installation or removal)".
159 Enables debugging output. Probably not hugely interesting.
161 \fB---\fR \fIvirt-server virt-server-arg\fR...
162 Specifies the virtualisation regime server, as a command and arguments
163 to invoke. All the remaining arguments and options after
165 are passed to the virtualisation server program.
168 Some options which come in variants with and without
170 These specify paths on the testbed and the host, respectively. The
171 data will be copied by
173 to where it is needed.
176 During a normal test run, one line is printed for each test. This
177 consists of the name of the test, some horizontal whitespace, and
184 where the pass/fail indication is separated by any reason by some
185 horizontal whitespace.
189 will be reported when the name of the test is not known or not
190 applicable: for example, when there are no tests in the package, or a
191 there is a test stanza which contains features not understood by this
196 will appear where the name of the test should be.
201 2 at least one test skipped
203 4 at least one test failed
205 6 at least one test failed and at least one test skipped
207 8 no tests in this package
213 20 other unexpected failures including bad usage
216 \fBadt-virt-chroot\fR(1)
219 This tool still lacks many important features.
221 .SH AUTHORS AND COPYRIGHT
222 This manpage is part of autopkgtest, a tool for testing Debian binary
223 packages. autopkgtest is Copyright (C) 2006 Canonical Ltd and others.
225 See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
226 contributors and full copying conditions.