= USAGE =

== Standard case ==

Put the following into debian/tests/control:

    Test-Command: /usr/share/pkg-perl-autopkgtest/runner build-deps
    Depends: @, @builddeps@, pkg-perl-autopkgtest

    Test-Command: /usr/share/pkg-perl-autopkgtest/runner runtime-deps
    Depends: @, pkg-perl-autopkgtest

    Test-Command: /usr/share/pkg-perl-autopkgtest/runner runtime-deps-and-recommends
    Depends: @, pkg-perl-autopkgtest
    Restrictions: needs-recommends

    Test-Command: /usr/share/pkg-perl-autopkgtest/runner heavy-deps
    Depends: @, pkg-perl-autopkgtest, pkg-perl-autopkgtest-heavy

This will run all "standard" tests in /usr/share/pkg-perl-autopkgtest/*.d/*.

In case autopkgtest gains support for an Include directive, this can be
replaced by a single line. Cf. #759753.


== Custom cases ==

In case you want other tests, need other dependencies or restrictions, you
can just add them according the the spec manually.

== 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/test-files'.

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/module-name'.
