diff options
| author | Anibal Limon <anibal@limonsoftware.com> | 2025-06-19 16:13:15 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-06-30 17:44:21 +0100 |
| commit | a904fe5a034cefc18f64a7c0f5feb5a107c14ae4 (patch) | |
| tree | b3afd022f8b926e5cc1c6fb1e6314e84570eaa0b /documentation/test-manual | |
| parent | c1ffedae4658492765058a0a6c6c8f74d388e871 (diff) | |
| download | poky-a904fe5a034cefc18f64a7c0f5feb5a107c14ae4.tar.gz | |
test-manual/ptest: Add info about fail state of ptest-runner/ptests
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]
(From yocto-docs rev: 0d1fd79019883f366d796b58a01679297d7a5508)
Signed-off-by: Anibal Limon <anibal@limonsoftware.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/test-manual')
| -rw-r--r-- | documentation/test-manual/ptest.rst | 17 |
1 files changed, 12 insertions, 5 deletions
diff --git a/documentation/test-manual/ptest.rst b/documentation/test-manual/ptest.rst index 2c021af515..4e6be35df5 100644 --- a/documentation/test-manual/ptest.rst +++ b/documentation/test-manual/ptest.rst | |||
| @@ -46,13 +46,19 @@ Running ptest | |||
| 46 | ============= | 46 | ============= |
| 47 | 47 | ||
| 48 | The ``ptest-runner`` package installs a shell script that loops through | 48 | The ``ptest-runner`` package installs a shell script that loops through |
| 49 | all installed ptest test suites and runs them in sequence. Consequently, | 49 | all installed ptest test suites and runs them in sequence. |
| 50 | you might want to add this package to your image. | 50 | |
| 51 | During the execution ``ptest-runner`` keeps count of total and failed | ||
| 52 | ``ptests``. At end the execution summary is written to the console. | ||
| 53 | If any of the ``run-ptest`` fails, ``ptest-runner`` returns '1'. | ||
| 54 | |||
| 55 | Consequently, you might want to add ``ptest-runner`` to your image. | ||
| 56 | |||
| 51 | 57 | ||
| 52 | Getting Your Package Ready | 58 | Getting Your Package Ready |
| 53 | ========================== | 59 | ========================== |
| 54 | 60 | ||
| 55 | In order to enable a recipe to run installed ptests on target hardware, | 61 | In order to enable a recipe to run installed ``ptests`` on target hardware, |
| 56 | you need to prepare the recipes that build the packages you want to | 62 | you need to prepare the recipes that build the packages you want to |
| 57 | test. Here is what you have to do for each recipe: | 63 | test. Here is what you have to do for each recipe: |
| 58 | 64 | ||
| @@ -77,8 +83,9 @@ test. Here is what you have to do for each recipe: | |||
| 77 | 83 | ||
| 78 | - *Create run-ptest:* This script starts your test. Locate the | 84 | - *Create run-ptest:* This script starts your test. Locate the |
| 79 | script where you will refer to it using | 85 | script where you will refer to it using |
| 80 | :term:`SRC_URI`. Here is an | 86 | :term:`SRC_URI`. Be sure ``run-ptest`` exits with 0 to mark it |
| 81 | example that starts a test for ``dbus``:: | 87 | as successfully executed otherwise will be marked as fail. |
| 88 | Here is an example that starts a test for ``dbus``:: | ||
| 82 | 89 | ||
| 83 | #!/bin/sh | 90 | #!/bin/sh |
| 84 | cd test | 91 | cd test |
