= USAGE =

== Standard case ==

Put the following into the source section of debian/control:

    Testsuite: autopkgtest-pkg-perl

This will activate an implicit test control file in autopkgtest that
will run all "standard" tests in /usr/share/pkg-perl-autopkgtest/*.d/*.
An explicit 'debian/tests/control' file does not need to be provided.

== Custom cases ==

In case you want other tests, or need other dependencies or
restrictions, you can add an explicit test control file
and list them according the the spec manually. You can use
/usr/share/doc/pkg-perl-autopkgtest/examples/default-tests-control as
a starting point.

== Skipping tests ==

If one of the standard tests has an expected failure, you can tell the
test runner to ignore it by listing it in 'debian/tests/pkg-perl/SKIP'.
The file can contain empty lines and comment lines starting with the '#' sign.

== Configuration ==

If your test suite needs files other than the contents of directory 't/' for
running prove, then you should list all files or directories to be copied to
the test running directory in the file 'debian/tests/pkg-perl/test-files'.
Empty lines and #-style comment lines are supported.

If there are just a few test files in the main test suite that fail smoke.t,
you can ignore those by adding them to 'debian/tests/pkg-perl/skip-smoke',
one per line. Empty lines and #-style comments are supported. Note that
t/97_meta.t, t/04critic.t, t/boilerplate.t, t/pod.t, and t/pod-coverage.t
are skipped automatically unless you provide a skip list.

If the runtime-deps.d/use.t test fails to get the main module of your
package right, you can customize that by putting the right name in
'debian/tests/pkg-perl/module-name'.

If there are just a few modules that fail syntax.t, you can ignore those
by adding them to 'debian/tests/pkg-perl/skip-syntax'. The lines are
matched as fixed substrings (not regular expressions.) Empty lines and
#-style comments are supported.
