summaryrefslogtreecommitdiffstats
path: root/documentation/test-manual/test-manual-intro.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/test-manual/test-manual-intro.rst')
-rw-r--r--documentation/test-manual/test-manual-intro.rst22
1 files changed, 0 insertions, 22 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