|
|
7.
|
|
|
Below we are having a look at the ``glib2.0`` source package. In a very simple case the file would look like this::
|
|
|
|
|
Hieronder bekijken we het ``glib2.0``-bronpakket. In een zeer eenvoudig geval zou het bestand er als volgt uitzien::
|
|
Translated and reviewed by
Hannie Dumoleyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:22
|
|
|
8.
|
|
|
For the test in ``debian/tests/build`` this would ensure that the packages ``libglib2.0-dev`` and ``build-essential`` are installed.
|
|
|
|
|
Voor de test in ``debian/tests/build`` zou dit ervoor zorgen dat de pakketten ``libglib2.0-dev`` en ``build-essential`` geïnstalleerd zijn.
|
|
Translated and reviewed by
Hannie Dumoleyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:28
|
|
|
9.
|
|
|
You can use ``@`` in the ``Depends`` line to indicate that you want all the packages installed which are built by the source package in question.
|
|
|
|
|
U kunt ``@`` in de regel ``Depends`` gebruiken om aan te geven dat u alle pakketten die gebouwd worden door het betreffende bronpakket geïnstalleerd wilt hebben.
|
|
Translated and reviewed by
Hannie Dumoleyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:31
|
|
|
10.
|
|
|
The actual tests
|
|
|
|
|
De werkelijke testen
|
|
Translated and reviewed by
Hannie Dumoleyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:37
|
|
|
11.
|
|
|
The accompanying test for the example above might be:
|
|
|
|
|
De bijbehorende test voor het voorbeeld hierboven zou kunnen zijn:
|
|
Translated and reviewed by
Hannie Dumoleyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:39
|
|
|
12.
|
|
|
Here a very simple piece of C code is written to a temporary directory. Then this is compiled with system libraries (using flags and library paths as provided by `pkg-config`). Then the compiled binary, which just exercises some parts of core glib functionality, is run.
|
|
|
|
|
Hier wordt een zeer eenvoudig stukje C-code geschreven naar een tijdelijke map. Daarna wordt dit gecompileerd met systeembibliotheken (gebruik makend van vlaggen en bibliotheekpaden zoals geboden door `pkg-config`). Daarna wordt het gecompileerde binaire bestand, dat alleen maar een paar onderdelen van de kernfunctionaliteit van glib uitoefent, uitgevoerd.
|
|
Translated and reviewed by
Hannie Dumoleyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:71
|
|
|
13.
|
|
|
While this test is very small and simple, it covers quite a lot: that your -dev package has all necessary dependencies, that your package installs working pkg-config files, headers and libraries are put into the right place, or that the compiler and linker work. This helps to uncover critical issues early on.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:76
|
|
|
14.
|
|
|
Executing the test
|
|
|
|
|
De test uitvoeren
|
|
Translated and reviewed by
Hannie Dumoleyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:82
|
|
|
15.
|
|
|
While the test script can be easily executed on its own, it is strongly recommended to actually use ``autopkgtest`` from the ``autopkgtest`` package for verifying that your test works; otherwise, if it fails in the Ubuntu Continuous Integration (CI) system, it will not land in Ubuntu. This also avoids cluttering your workstation with test packages or test configuration if the test does something more intrusive than the simple example above.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:84
|
|
|
16.
|
|
|
The `README.running-tests <running_tests_local_>`_ (`online version <DEP8_>`_) documentation explains all available testbeds (schroot, LXD, QEMU, etc.) and the most common scenarios how to run your tests with ``autopkgtest``, e. g. with locally built binaries, locally modified tests, etc.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:91
|
