|
|
33.
|
|
|
Getting the test into Ubuntu
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:159
|
|
|
34.
|
|
|
The process of submitting an autopkgtest for a package is largely similar to :doc:`fixing a bug in Ubuntu<./fixing-a-bug>`. Essentially you simply:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:161
|
|
|
35.
|
|
|
run ``bzr branch ubuntu:<packagename>``,
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:164
|
|
|
36.
|
|
|
edit ``debian/control`` to enable the tests,
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:165
|
|
|
37.
|
|
|
add the ``debian/tests`` directory,
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:166
|
|
|
38.
|
|
|
write the ``debian/tests/control`` based on the `DEP 8 Specification <dep8_>`_,
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:167
|
|
|
39.
|
|
|
add your test case(s) to ``debian/tests``,
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:168
|
|
|
40.
|
|
|
commit your changes, push them to Launchpad, propose a merge and get it reviewed just like any other improvement in a source package.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:169
|
|
|
41.
|
|
|
What you can do
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:174
|
|
|
42.
|
|
|
The Ubuntu Engineering team put together a `list of required test-cases <requiredtests_>`_, where packages which need tests are put into different categories. Here you can find examples of these tests and easily assign them to yourself.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/auto-pkg-test.rst:176
|
