path: root/dh_auto_test
diff options
authorJoey Hess <>2009-06-28 15:40:15 -0400
committerJoey Hess <>2009-06-28 15:40:15 -0400
commit93c1062bc3ee340fcd7318e91fe9758d86b760f3 (patch)
tree5ca5f93c23c84fb2c3f0ce3a4199e57c01f422d3 /dh_auto_test
parente0ed03ff224ee3a8053094f02bcd02d4dd3fa358 (diff)
minimal build system option documentation
Diffstat (limited to 'dh_auto_test')
1 files changed, 10 insertions, 6 deletions
diff --git a/dh_auto_test b/dh_auto_test
index e68bf09..6caf393 100755
--- a/dh_auto_test
+++ b/dh_auto_test
@@ -11,16 +11,17 @@ use Debian::Debhelper::Dh_Buildsystems;
-B<dh_auto_test> [S<I<debhelper options>>] [S<B<--> I<params>>]
+B<dh_auto_test> [S<I<build system options>>] [S<I<debhelper options>>] [S<B<--> I<params>>]
dh_auto_test is a debhelper program that tries to automatically run a
-package's test suite. If there's a Makefile and it contains a "test"
-or "check" target, then this is done by running make (or MAKE, if the
-environment variable is set). If the test suite fails, the command will
-exit nonzero. If there's no test suite, it will exit zero without doing
+package's test suite. It does so by running the appropriate command for the
+build system it detects the package uses. For example, if there's a
+Makefile and it contains a "test" or "check" target, then this is done by
+running make (or MAKE, if the environment variable is set). If the test
+suite fails, the command will exit nonzero. If there's no test suite, it
+will exit zero without doing anything.
This is intended to work for about 90% of packages with a test suite. If it
doesn't work, you're encouraged to skip using dh_auto_test at all, and
@@ -28,6 +29,9 @@ just run the test suite manually.
=head1 OPTIONS
+See L<debhelper(7)/BUILD SYSTEM OPTIONS> for a list of common build
+system selection and control options.
=over 4
=item B<--> I<params>