summaryrefslogtreecommitdiffstats
path: root/documentation/test-manual
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2020-11-19 10:58:29 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-11-20 14:32:25 +0000
commit95b2d8a7fdb31e65796e75306365da74881e987b (patch)
treedfe9a6b2e9bbea9170702657d04e86b6d3e0c7ac /documentation/test-manual
parent043592a585ef6dab73e285985b381a11b91570a8 (diff)
downloadpoky-95b2d8a7fdb31e65796e75306365da74881e987b.tar.gz
test-manual: remove unused labels
(From yocto-docs rev: 3f7a065dafd24a3c1e6b7f68b522352606f8fd7b) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/test-manual')
-rw-r--r--documentation/test-manual/test-manual-intro.rst22
-rw-r--r--documentation/test-manual/test-manual-test-process.rst2
-rw-r--r--documentation/test-manual/test-manual-understand-autobuilder.rst20
3 files changed, 0 insertions, 44 deletions
diff --git a/documentation/test-manual/test-manual-intro.rst b/documentation/test-manual/test-manual-intro.rst
index 25b79f7a04..b6d1305916 100644
--- a/documentation/test-manual/test-manual-intro.rst
+++ b/documentation/test-manual/test-manual-intro.rst
@@ -4,8 +4,6 @@
4The Yocto Project Test Environment Manual 4The Yocto Project Test Environment Manual
5***************************************** 5*****************************************
6 6
7.. _test-welcome:
8
9Welcome 7Welcome
10======= 8=======
11 9
@@ -45,8 +43,6 @@ engineers:
45 Jenkins, or others. This repository has a branch per release of the 43 Jenkins, or others. This repository has a branch per release of the
46 project defining the tests to run on a per release basis. 44 project defining the tests to run on a per release basis.
47 45
48.. _test-yocto-project-autobuilder-overview:
49
50Yocto Project Autobuilder Overview 46Yocto Project Autobuilder Overview
51================================== 47==================================
52 48
@@ -88,8 +84,6 @@ topology that includes a controller and a cluster of workers:
88.. image:: figures/ab-test-cluster.png 84.. image:: figures/ab-test-cluster.png
89 :align: center 85 :align: center
90 86
91.. _test-project-tests:
92
93Yocto Project Tests - Types of Testing Overview 87Yocto Project Tests - Types of Testing Overview
94=============================================== 88===============================================
95 89
@@ -169,8 +163,6 @@ thefollowing types of tests:
169 those new versions. If so, this target emails the maintainers with a 163 those new versions. If so, this target emails the maintainers with a
170 patch to let them know this is possible. 164 patch to let them know this is possible.
171 165
172.. _test-test-mapping:
173
174How Tests Map to Areas of Code 166How Tests Map to Areas of Code
175============================== 167==============================
176 168
@@ -326,8 +318,6 @@ directory at ``meta/lib/oeqa/selftest/cases`` directory.
326For oe-selftest. bitbake testcases reside in the ``lib/bb/tests/`` 318For oe-selftest. bitbake testcases reside in the ``lib/bb/tests/``
327directory. 319directory.
328 320
329.. _bitbake-selftest-example:
330
331``bitbake-selftest`` 321``bitbake-selftest``
332-------------------- 322--------------------
333 323
@@ -354,8 +344,6 @@ Bitbake selftests are straightforward python unittest. Refer to the
354Python unittest documentation for additional information on writing 344Python unittest documentation for additional information on writing
355these tests at: https://docs.python.org/3/library/unittest.html. 345these tests at: https://docs.python.org/3/library/unittest.html.
356 346
357.. _oe-selftest-example:
358
359``oe-selftest`` 347``oe-selftest``
360--------------- 348---------------
361 349
@@ -399,8 +387,6 @@ builds. There is no data store available for these tests since the tests
399launch the ``bitbake`` command and exist outside of its context. As a 387launch the ``bitbake`` command and exist outside of its context. As a
400result, common bitbake library functions (bb.\*) are also unavailable. 388result, common bitbake library functions (bb.\*) are also unavailable.
401 389
402.. _testimage-example:
403
404``testimage`` 390``testimage``
405------------- 391-------------
406 392
@@ -429,8 +415,6 @@ To ensure certain test or package dependencies are met, you can use the
429in this example would only make sense if python3-core is installed in 415in this example would only make sense if python3-core is installed in
430the image. 416the image.
431 417
432.. _testsdk_ext-example:
433
434``testsdk_ext`` 418``testsdk_ext``
435--------------- 419---------------
436 420
@@ -463,8 +447,6 @@ In this example, the ``devtool``
463command is tested to see whether a sample application can be built with 447command is tested to see whether a sample application can be built with
464the ``devtool build`` command within the eSDK. 448the ``devtool build`` command within the eSDK.
465 449
466.. _testsdk-example:
467
468``testsdk`` 450``testsdk``
469----------- 451-----------
470 452
@@ -488,8 +470,6 @@ In this example, if nativesdk-python3-core has been installed into the SDK, the
488the python3 interpreter with a basic command to check it is working 470the python3 interpreter with a basic command to check it is working
489correctly. The test would only run if python3 is installed in the SDK. 471correctly. The test would only run if python3 is installed in the SDK.
490 472
491.. _oe-build-perf-test-example:
492
493``oe-build-perf-test`` 473``oe-build-perf-test``
494---------------------- 474----------------------
495 475
@@ -517,8 +497,6 @@ This example shows how three specific parsing timings are
517measured, with and without various caches, to show how BitBake's parsing 497measured, with and without various caches, to show how BitBake's parsing
518performance trends over time. 498performance trends over time.
519 499
520.. _test-writing-considerations:
521
522Considerations When Writing Tests 500Considerations When Writing Tests
523================================= 501=================================
524 502
diff --git a/documentation/test-manual/test-manual-test-process.rst b/documentation/test-manual/test-manual-test-process.rst
index b0817b091b..82b9bb441b 100644
--- a/documentation/test-manual/test-manual-test-process.rst
+++ b/documentation/test-manual/test-manual-test-process.rst
@@ -4,8 +4,6 @@
4Project Testing and Release Process 4Project Testing and Release Process
5*********************************** 5***********************************
6 6
7.. _test-daily-devel:
8
9Day to Day Development 7Day to Day Development
10====================== 8======================
11 9
diff --git a/documentation/test-manual/test-manual-understand-autobuilder.rst b/documentation/test-manual/test-manual-understand-autobuilder.rst
index 2444333761..698a266eef 100644
--- a/documentation/test-manual/test-manual-understand-autobuilder.rst
+++ b/documentation/test-manual/test-manual-understand-autobuilder.rst
@@ -73,8 +73,6 @@ The ``config.json`` file is processed by the scripts in the Helper
73repository in the ``scripts`` directory. The following section details 73repository in the ``scripts`` directory. The following section details
74how this works. 74how this works.
75 75
76.. _test-autobuilder-target-exec-overview:
77
78Autobuilder Target Execution Overview 76Autobuilder Target Execution Overview
79===================================== 77=====================================
80 78
@@ -135,16 +133,12 @@ roughly consist of:
135 This is another call into the Helper scripts where its expected that 133 This is another call into the Helper scripts where its expected that
136 the main functionality of this target will be executed. 134 the main functionality of this target will be executed.
137 135
138.. _test-autobuilder-tech:
139
140Autobuilder Technology 136Autobuilder Technology
141====================== 137======================
142 138
143The Autobuilder has Yocto Project-specific functionality to allow builds 139The Autobuilder has Yocto Project-specific functionality to allow builds
144to operate with increased efficiency and speed. 140to operate with increased efficiency and speed.
145 141
146.. _test-clobberdir:
147
148clobberdir 142clobberdir
149---------- 143----------
150 144
@@ -155,8 +149,6 @@ which is run under ``ionice -c 3``. For example, the deletion only
155happens when there is idle IO capacity on the Worker. The Autobuilder 149happens when there is idle IO capacity on the Worker. The Autobuilder
156Worker Janitor runs this deletion. See :ref:`test-manual/test-manual-understand-autobuilder:Autobuilder Worker Janitor`. 150Worker Janitor runs this deletion. See :ref:`test-manual/test-manual-understand-autobuilder:Autobuilder Worker Janitor`.
157 151
158.. _test-autobuilder-clone-cache:
159
160Autobuilder Clone Cache 152Autobuilder Clone Cache
161----------------------- 153-----------------------
162 154
@@ -167,8 +159,6 @@ during clones first, then "topped up" with later revisions from any
167upstream when necessary. The cache is maintained by the Autobuilder 159upstream when necessary. The cache is maintained by the Autobuilder
168Worker Janitor. See :ref:`test-manual/test-manual-understand-autobuilder:Autobuilder Worker Janitor`. 160Worker Janitor. See :ref:`test-manual/test-manual-understand-autobuilder:Autobuilder Worker Janitor`.
169 161
170.. _test-autobuilder-worker-janitor:
171
172Autobuilder Worker Janitor 162Autobuilder Worker Janitor
173-------------------------- 163--------------------------
174 164
@@ -177,8 +167,6 @@ operations, including background file deletion at IO idle (see :ref:`test-manual
177maintainenance of a cache of cloned repositories to improve the speed 167maintainenance of a cache of cloned repositories to improve the speed
178the system can checkout repositories. 168the system can checkout repositories.
179 169
180.. _test-shared-dl-dir:
181
182Shared DL_DIR 170Shared DL_DIR
183------------- 171-------------
184 172
@@ -187,8 +175,6 @@ between them. This reduces network accesses from the system and allows
187the build to be sped up. Usage of the directory within the build system 175the build to be sped up. Usage of the directory within the build system
188is designed to be able to be shared over NFS. 176is designed to be able to be shared over NFS.
189 177
190.. _test-shared-sstate-cache:
191
192Shared SSTATE_DIR 178Shared SSTATE_DIR
193----------------- 179-----------------
194 180
@@ -197,8 +183,6 @@ directory to be shared between them. This means once a Worker has built
197an artifact, all the others can benefit from it. Usage of the directory 183an artifact, all the others can benefit from it. Usage of the directory
198within the directory is designed for sharing over NFS. 184within the directory is designed for sharing over NFS.
199 185
200.. _test-resulttool:
201
202Resulttool 186Resulttool
203---------- 187----------
204 188
@@ -213,8 +197,6 @@ reports of the test results and compare different result files.
213 197
214For details, see :yocto_wiki:`/wiki/Resulttool`. 198For details, see :yocto_wiki:`/wiki/Resulttool`.
215 199
216.. _test-run-config-tgt-execution:
217
218run-config Target Execution 200run-config Target Execution
219=========================== 201===========================
220 202
@@ -264,8 +246,6 @@ of post-build steps, including:
264 :ref:`test-manual/test-manual-understand-autobuilder:clobberdir` if the build was successful, 246 :ref:`test-manual/test-manual-understand-autobuilder:clobberdir` if the build was successful,
265 else rename it to "build-renamed" for potential future debugging. 247 else rename it to "build-renamed" for potential future debugging.
266 248
267.. _test-deploying-yp-autobuilder:
268
269Deploying Yocto Autobuilder 249Deploying Yocto Autobuilder
270=========================== 250===========================
271 251