mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-09 05:29:32 +00:00
Code Issues Projects Releases Wiki Activity

ref-manual/packages: move ptest section to the test-manual

Browse Source 
[ YOCTO #15106 ]

It makes more sense to document ptests in the test-manual. Since ptests
are still related to packages, keep a link to ptests from packages.rst
to the test-manual.

Reported-by: Yoann Congal <yoann.congal@smile.fr>
(From yocto-docs rev: b79d1c8d501418d20c024c92b0ace755dd6b1c88)

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit b389c06b709e4791e1cce5e8a5b58f6b0cd03a14)
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:16 +01:00
committed by Steve Sakoman
parent 843c4a8de7
commit 587d779d56
10 changed files with 126 additions and 117 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/classes.rst
+2 -2
View File
@@ -2626,7 +2626,7 @@ runtime tests for recipes that build software that provides these tests.
This class is intended to be inherited by individual recipes. However,
the class' functionality is largely disabled unless "ptest" appears in
:term:`DISTRO_FEATURES`. See the
":ref:`dev-manual/packages:testing packages with ptest`"
":ref:`test-manual/ptest:testing packages with ptest`"
section in the Yocto Project Development Tasks Manual for more information
on ptest.
@@ -2650,7 +2650,7 @@ Enables package tests (ptests) specifically for GNOME packages, which
have tests intended to be executed with ``gnome-desktop-testing``.
For information on setting up and running ptests, see the
":ref:`dev-manual/packages:testing packages with ptest`"
":ref:`test-manual/ptest:testing packages with ptest`"
section in the Yocto Project Development Tasks Manual.
.. _ref-classes-python3-dir:
documentation/ref-manual/features.rst
+1 -1
View File
@@ -207,7 +207,7 @@ metadata, as extra layers can define their own:
- *ptest:* Enables building the package tests where supported by
individual recipes. For more information on package tests, see the
":ref:`dev-manual/packages:testing packages with ptest`" section
":ref:`test-manual/ptest:testing packages with ptest`" section
in the Yocto Project Development Tasks Manual.
- *pulseaudio:* Include support for
documentation/ref-manual/qa-checks.rst
+1 -1
View File
@@ -791,7 +791,7 @@ Errors and Warnings
This check will detect if the source of the package contains some
upstream-provided tests and, if so, that ptests are implemented for this
recipe. See the ":ref:`dev-manual/packages:testing packages with ptest`"
recipe. See the ":ref:`test-manual/ptest:testing packages with ptest`"
section in the Yocto Project Development Tasks Manual. See also the
":ref:`ref-classes-ptest`" section.
documentation/ref-manual/release-process.rst
+1 -1
View File
@@ -175,7 +175,7 @@ consists of the following pieces:
operation and functions. However, the test can also use the IP
address of a machine to test.
- :ref:`ptest <dev-manual/packages:testing packages with ptest>`:
- :ref:`ptest <test-manual/ptest:testing packages with ptest>`:
Runs tests against packages produced during the build for a given
piece of software. The test allows the packages to be run within a
target image.
documentation/ref-manual/variables.rst
+1 -1
View File
@@ -6891,7 +6891,7 @@ system and gives an overview of their function and contents.
:term:`PTEST_ENABLED`
Specifies whether or not :ref:`Package
Test <dev-manual/packages:testing packages with ptest>` (ptest)
Test <test-manual/ptest:testing packages with ptest>` (ptest)
functionality is enabled when building a recipe. You should not set
this variable directly. Enabling and disabling building Package Tests
at build time should be done by adding "ptest" to (or removing it