* [PATCHv5] test-manual/ptest: Add info about fail state of ptest-runner/ptests
@ 2025-06-19 16:13 Anibal Limon
2025-07-01 8:37 ` Antonin Godard
0 siblings, 1 reply; 2+ messages in thread
From: Anibal Limon @ 2025-06-19 16:13 UTC (permalink / raw)
To: docs; +Cc: antonin.godard, erik.schumacher, yoann.congal, Anibal Limon
On the ML was pointed about no specific information about
ptest-runner/ptests so improve docs around.
https://lists.yoctoproject.org/g/yocto-patches/message/1622
[YOCTO #15832]
Signed-off-by: Anibal Limon <anibal@limonsoftware.com>
---
documentation/test-manual/ptest.rst | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/documentation/test-manual/ptest.rst b/documentation/test-manual/ptest.rst
index 2c021af51..4e6be35df 100644
--- a/documentation/test-manual/ptest.rst
+++ b/documentation/test-manual/ptest.rst
@@ -46,13 +46,19 @@ Running ptest
=============
The ``ptest-runner`` package installs a shell script that loops through
-all installed ptest test suites and runs them in sequence. Consequently,
-you might want to add this package to your image.
+all installed ptest test suites and runs them in sequence.
+
+During the execution ``ptest-runner`` keeps count of total and failed
+``ptests``. At end the execution summary is written to the console.
+If any of the ``run-ptest`` fails, ``ptest-runner`` returns '1'.
+
+Consequently, you might want to add ``ptest-runner`` to your image.
+
Getting Your Package Ready
==========================
-In order to enable a recipe to run installed ptests on target hardware,
+In order to enable a recipe to run installed ``ptests`` on target hardware,
you need to prepare the recipes that build the packages you want to
test. Here is what you have to do for each recipe:
@@ -77,8 +83,9 @@ test. Here is what you have to do for each recipe:
- *Create run-ptest:* This script starts your test. Locate the
script where you will refer to it using
- :term:`SRC_URI`. Here is an
- example that starts a test for ``dbus``::
+ :term:`SRC_URI`. Be sure ``run-ptest`` exits with 0 to mark it
+ as successfully executed otherwise will be marked as fail.
+ Here is an example that starts a test for ``dbus``::
#!/bin/sh
cd test
--
2.39.5
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCHv5] test-manual/ptest: Add info about fail state of ptest-runner/ptests
2025-06-19 16:13 [PATCHv5] test-manual/ptest: Add info about fail state of ptest-runner/ptests Anibal Limon
@ 2025-07-01 8:37 ` Antonin Godard
0 siblings, 0 replies; 2+ messages in thread
From: Antonin Godard @ 2025-07-01 8:37 UTC (permalink / raw)
To: docs, Anibal Limon
Cc: Thomas Petazzoni, Antonin Godard, erik.schumacher, yoann.congal
On Thu, 19 Jun 2025 16:13:15 +0000, Anibal Limon wrote:
> On the ML was pointed about no specific information about
> ptest-runner/ptests so improve docs around.
>
> https://lists.yoctoproject.org/g/yocto-patches/message/1622
>
> [YOCTO #15832]
>
> [...]
Applied, thanks!
[1/1] test-manual/ptest: Add info about fail state of ptest-runner/ptests
commit: 0d1fd79019883f366d796b58a01679297d7a5508
Best regards,
--
Antonin Godard <antonin.godard@bootlin.com>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-07-01 8:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-19 16:13 [PATCHv5] test-manual/ptest: Add info about fail state of ptest-runner/ptests Anibal Limon
2025-07-01 8:37 ` Antonin Godard
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.