|
|
7.
|
|
|
Below we are having a look at the ``glib2.0`` source package. In a very simple case the file would look like this::
|
|
|
|
|
下面我們會看一看 ``glib2.0`` 原始碼套件。在一個非常简單的例子中該檔案會是這樣子：
|
|
Translated by
Z.X.Lyn
|
|
Reviewed by
Z.X.Lyn
|
|
|
|
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.
|
|
|
|
|
爲了 ``debian/tests/build`` 中的測試，這會確保套件 ``libglib2.0-dev`` 及 ``build-essential`` 會被安装。
|
|
Translated and reviewed by
Z.X.Lyn
|
|
|
|
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.
|
|
|
|
|
您可以在 ``Depends`` 行裏使用 ``@`` 来指明所有此套件依赖的需要构建的套件。
|
|
Translated by
Z.X.Lyn
|
|
Reviewed by
Z.X.Lyn
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:31
|
|
|
10.
|
|
|
The actual tests
|
|
|
|
|
實際的測試
|
|
Translated and reviewed by
Howard Chan
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:37
|
|
|
11.
|
|
|
The accompanying test for the example above might be:
|
|
|
|
|
上面例子的随附測試可能是：
|
|
Translated and reviewed by
Howard Chan
|
|
|
|
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.
|
|
|
|
|
在這裏一篇非常简單的 C 代碼會被寫到一個臨時資料夹裏。然後（利用由 `pkg-config` 提供的標誌及庫路徑）代码會用系統庫編譯。編譯後，這個只實現了一部分核心 glib 功能的程序會被測試運行。
|
|
Translated and reviewed by
Z.X.Lyn
|
|
|
|
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
|
|
|
|
|
運行測試
|
|
Translated and reviewed by
Howard Chan
|
|
|
|
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
|
