1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-08 05:09:24 +00:00

ref-manual: move runtime-testing section to the test-manual

In the same fashion as the previous commit ("ref-manual/packages: move
ptest section to the test-manual"), move the runtime testing section of
the development tasks manual to the test environment manual.

Add a link to it from the test-manual/intro document.

(From yocto-docs rev: 79aa34db34def525a11c41d951365bcb891318c4)

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit 6b44257874858db3aa426d3e84a79c41cb4937a3)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
Antonin Godard
2024-12-26 16:20:17 +01:00
committed by Steve Sakoman
parent 3f782b6e45
commit 7117d115ea
10 changed files with 29 additions and 26 deletions
+2 -2
View File
@@ -3212,8 +3212,8 @@ after it is built, you can set :term:`TESTIMAGE_AUTO`::
TESTIMAGE_AUTO = "1"
For information on how to enable, run, and create new tests, see the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual.
.. _ref-classes-testsdk:
+2 -2
View File
@@ -119,8 +119,8 @@ Here is a list of supported recipes:
deployed to a separate partition so that you can boot into it and use
it to deploy a second image to be tested. You can find more
information about runtime testing in the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual.
- ``core-image-testmaster-initramfs``: A RAM-based Initial Root
Filesystem (:term:`Initramfs`) image tailored for use with the
+2 -2
View File
@@ -148,8 +148,8 @@ Additionally, because the test strategies are visible to you as a
developer, you can validate your projects. This section overviews the
available test infrastructure used in the Yocto Project. For information
on how to run available tests on your projects, see the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual.
The QA/testing infrastructure is woven into the project to the point
where core developers take some of it for granted. The infrastructure
+4 -4
View File
@@ -616,8 +616,8 @@ information on how the root filesystem is created.
Boots an image and performs runtime tests within the image. For
information on automatically testing images, see the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual.
.. _ref-tasks-testimage_auto:
@@ -629,8 +629,8 @@ after it has been built. This task is enabled when you set
:term:`TESTIMAGE_AUTO` equal to "1".
For information on automatically testing images, see the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual.
Kernel-Related Tasks
====================
+10 -10
View File
@@ -9143,8 +9143,8 @@ system and gives an overview of their function and contents.
file.
For more information on testing images, see the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual.
:term:`TEST_SERIALCONTROL_CMD`
For automated hardware testing, specifies the command to use to
@@ -9215,8 +9215,8 @@ system and gives an overview of their function and contents.
TEST_SUITES = "test_A test_B"
For more information on testing images, see the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual.
:term:`TEST_TARGET`
Specifies the target controller to use when running tests against a
@@ -9234,8 +9234,8 @@ system and gives an overview of their function and contents.
You can provide the following arguments with :term:`TEST_TARGET`:
- *"qemu":* Boots a QEMU image and runs the tests. See the
":ref:`dev-manual/runtime-testing:enabling runtime tests on qemu`" section
in the Yocto Project Development Tasks Manual for more
":ref:`test-manual/runtime-testing:enabling runtime tests on qemu`" section
in the Yocto Project Test Environment Manual for more
information.
- *"simpleremote":* Runs the tests on target hardware that is
@@ -9250,8 +9250,8 @@ system and gives an overview of their function and contents.
``meta/lib/oeqa/controllers/simpleremote.py``.
For information on running tests on hardware, see the
":ref:`dev-manual/runtime-testing:enabling runtime tests on hardware`"
section in the Yocto Project Development Tasks Manual.
":ref:`test-manual/runtime-testing:enabling runtime tests on hardware`"
section in the Yocto Project Test Environment Manual.
:term:`TEST_TARGET_IP`
The IP address of your hardware under test. The :term:`TEST_TARGET_IP`
@@ -9287,8 +9287,8 @@ system and gives an overview of their function and contents.
For more information
on enabling, running, and writing these tests, see the
":ref:`dev-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Development Tasks Manual and the
":ref:`test-manual/runtime-testing:performing automated runtime testing`"
section in the Yocto Project Test Environment Manual and the
":ref:`ref-classes-testimage`" section.
:term:`TESTIMAGE_FAILED_QA_ARTIFACTS`