|
|
4.
|
|
|
add the tests in ``debian/tests/``.
|
|
|
|
|
Lägg till testerna i ''debian/tests/''.
|
|
Translated by
Peter Ahlgren
|
|
Reviewed by
Joachim Johansson
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:11
|
|
|
5.
|
|
|
Testbed requirements
|
|
|
|
|
Kraven för testunderlaget
|
|
Translated by
Peter Ahlgren
|
|
Reviewed by
Joachim Johansson
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:15
|
|
|
6.
|
|
|
In ``debian/tests/control`` you specify what to expect from the testbed. So for example you list all the required packages for the tests, if the testbed gets broken during the build or if ``root`` permissions are required. The `DEP 8 specification <DEP8_>`_ lists all available options.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:17
|
|
|
7.
|
|
|
Below we are having a look at the ``glib2.0`` source package. In a very simple case the file would look like this::
|
|
|
|
|
Nedan tar vi en titt på källkodspaketet för ``glib2.0``. I ett väldigt enkelt fall skulle filen se ut så här::
|
|
Translated by
Peter Ahlgren
|
|
Reviewed by
Joachim Johansson
|
|
|
|
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.
|
|
|
|
|
För testet i ``debian/tests/build`` skulle detta säkerställa att paketen ``libglib2.0-dev`` och ``build-essential`` är installerade.
|
|
Translated by
Peter Ahlgren
|
|
Reviewed by
Joachim Johansson
|
|
|
|
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.
|
|
|
|
|
Du kan använda ``@`` på raden ``Depends`` för att indikera att du vill ha alla paket installerade som är byggda av källpaketet i fråga.
|
|
Translated by
Peter Ahlgren
|
|
Reviewed by
Joachim Johansson
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:31
|
|
|
10.
|
|
|
The actual tests
|
|
|
|
|
De riktiga testerna
|
|
Translated by
Joachim Johansson
|
|
Reviewed by
Peter Ahlgren
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:37
|
|
|
11.
|
|
|
The accompanying test for the example above might be:
|
|
|
|
|
Det åtföljande testet för exemplet ovan skulle vara:
|
|
Translated by
Peter Ahlgren
|
|
Reviewed by
Joachim Johansson
|
|
|
|
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.
|
|
|
|
|
Här är en enkel snutt C-kod som skrivs till en temporär mapp. Koden kompileras med systembiblioteken (med de flaggor och sökvägar som ges i 'pkg-config'). Sen körs den kompilerade binärfilen, som i det här fallet visar några funktioner från 'core glib'.
|
|
Translated and reviewed by
Peter Ahlgren
|
|
|
|
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
|
