From bcff406b2829ec792a690e31c6f6254d0c66fd7a Mon Sep 17 00:00:00 2001 From: Antonin Godard Date: Thu, 23 Jan 2025 16:48:03 +0100 Subject: [PATCH] test-manual/ptest: link to common framework ptest classes We document how to add ptest support for a recipe by inheriting the ptest class. We may as well tell the user to inherit a ptest class for a common framework which does most of the job for you. Suggested-by: Quentin Schulz Reviewed-by: Quentin Schulz (From yocto-docs rev: eb44bae3071b751820a6564f31a50ec1bfde5e42) Signed-off-by: Antonin Godard (cherry picked from commit 411b18e489a97ea4cde05613cdd4c86deb0cb8cb) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman --- documentation/test-manual/ptest.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/documentation/test-manual/ptest.rst b/documentation/test-manual/ptest.rst index dea1bad23b..2c021af515 100644 --- a/documentation/test-manual/ptest.rst +++ b/documentation/test-manual/ptest.rst @@ -61,6 +61,20 @@ test. Here is what you have to do for each recipe: inherit ptest + .. note:: + + Classes for common frameworks already exist in :term:`OpenEmbedded-Core + (OE-Core)`, such as: + + - :oe_git:`go-ptest ` + - :ref:`ref-classes-ptest-cargo` + - :ref:`ref-classes-ptest-gnome` + - :oe_git:`ptest-perl ` + - :oe_git:`ptest-python-pytest ` + + Inheriting these classes with the ``inherit`` keyword in your recipe will + make the next steps automatic. + - *Create run-ptest:* This script starts your test. Locate the script where you will refer to it using :term:`SRC_URI`. Here is an