mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 12:59:02 +02: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: 6b44257874858db3aa426d3e84a79c41cb4937a3) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
d720994f02
commit
d6ae2c0dec
|
@ -39,7 +39,6 @@ Yocto Project Development Tasks Manual
|
|||
external-scm
|
||||
read-only-rootfs
|
||||
build-quality
|
||||
runtime-testing
|
||||
debugging
|
||||
licenses
|
||||
security-subjects
|
||||
|
|
|
@ -248,8 +248,8 @@ A new automated image testing framework has been added through the
|
|||
framework replaces the older ``imagetest-qemu`` framework.
|
||||
|
||||
You can learn more about performing automated image tests 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.
|
||||
|
||||
.. _migration-1.5-build-history:
|
||||
|
||||
|
|
|
@ -3232,8 +3232,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:
|
||||
|
||||
|
|
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
|
@ -615,8 +615,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:
|
||||
|
||||
|
@ -628,8 +628,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
|
||||
====================
|
||||
|
|
|
@ -9305,8 +9305,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
|
||||
|
@ -9377,8 +9377,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
|
||||
|
@ -9396,8 +9396,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
|
||||
|
@ -9412,8 +9412,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`
|
||||
|
@ -9449,8 +9449,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`
|
||||
|
|
|
@ -13,6 +13,7 @@ Yocto Project Test Environment Manual
|
|||
intro
|
||||
test-process
|
||||
ptest
|
||||
runtime-testing
|
||||
understand-autobuilder
|
||||
reproducible-builds
|
||||
yocto-project-compatible
|
||||
|
|
|
@ -130,7 +130,9 @@ the following types of tests:
|
|||
$ bitbake image -c testimage
|
||||
|
||||
The tests use the :ref:`ref-classes-testimage`
|
||||
class and the :ref:`ref-tasks-testimage` task.
|
||||
class and the :ref:`ref-tasks-testimage` task. See the
|
||||
:ref:`test-manual/runtime-testing:Performing Automated Runtime Testing`
|
||||
section of the Yocto Project Test Environment Manual for more information.
|
||||
|
||||
- *Layer Testing:* The Autobuilder has the possibility to test whether
|
||||
specific layers work with the test of the system. The layers tested
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
|
||||
|
||||
************************************
|
||||
Performing Automated Runtime Testing
|
||||
************************************
|
||||
|
||||
|
@ -153,7 +154,7 @@ options are available:
|
|||
|
||||
If you choose "SystemdbootTarget", there are additional requirements
|
||||
and considerations. See the
|
||||
":ref:`dev-manual/runtime-testing:selecting systemdboottarget`" section, which
|
||||
":ref:`test-manual/runtime-testing:selecting systemdboottarget`" section, which
|
||||
follows, for more information.
|
||||
|
||||
- *"BeagleBoneTarget":* Choose "BeagleBoneTarget" if you are deploying
|
||||
|
@ -179,7 +180,7 @@ Selecting SystemdbootTarget
|
|||
|
||||
If you did not set :term:`TEST_TARGET` to "SystemdbootTarget", then you do
|
||||
not need any information in this section. You can skip down to the
|
||||
":ref:`dev-manual/runtime-testing:running tests`" section.
|
||||
":ref:`test-manual/runtime-testing:running tests`" section.
|
||||
|
||||
If you did set :term:`TEST_TARGET` to "SystemdbootTarget", you also need to
|
||||
perform a one-time setup of your controller image by doing the following:
|
Loading…
Reference in New Issue
Block a user