summaryrefslogtreecommitdiff
path: root/doc/develop/pytest
diff options
context:
space:
mode:
authorTom Rini <[email protected]>2025-11-24 09:34:29 -0600
committerTom Rini <[email protected]>2025-11-24 09:34:29 -0600
commit4a4871e3dc38f3f771d2713b805e79e6191b4297 (patch)
treef3cbb63c259f8cce92e87bf1a30b69c02b07c2dc /doc/develop/pytest
parent6e7d2399c8139f8e2d037e446236b8d8bdbca604 (diff)
parentc5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9 (diff)
Merge tag 'v2026.01-rc3' into next
Prepare v2026.01-rc3
Diffstat (limited to 'doc/develop/pytest')
-rw-r--r--doc/develop/pytest/usage.rst23
1 files changed, 14 insertions, 9 deletions
diff --git a/doc/develop/pytest/usage.rst b/doc/develop/pytest/usage.rst
index 596b0397379..7335a39b963 100644
--- a/doc/develop/pytest/usage.rst
+++ b/doc/develop/pytest/usage.rst
@@ -35,21 +35,26 @@ can be installed via the command
pip install -r requirements.txt
In order to execute certain tests on their supported platforms other tools
-will be required. The following is an incomplete list:
+will be required. The following packages may be needed:
-* gdisk
-* dfu-util
-* dtc
-* openssl
-* e2fsprogs
-* util-linux
+* cgpt
* coreutils
+* device-tree-compiler
+* dfu-util
* dosfstools
+* e2fsprogs
* efitools
+* fdisk
+* gdisk
+* libgnutls28-dev / gnutls-devel
* mount
* mtools
+* openssl
* sbsigntool
+* swig
* udisks2
+* util-linux
+* vboot-kernel-utils / vboot-utils
Please use the appropriate commands for your distribution to match these tools
up with the package that provides them.
@@ -63,7 +68,7 @@ The test script supports either:
Further details are described later.
The usage of the command ``sudo`` is not allowed in tests. Using elevated
-priviledges can lead to security concerns. Furthermore not all users may have
+privileges can lead to security concerns. Furthermore not all users may have
administrator rights. Therefore the command ``sudo`` must not be used in tests.
To create disk images we have helper functions located in
``test/py/tests/fs_helper.py`` which shall be used in any tests that require
@@ -387,7 +392,7 @@ to flash, pulsing the board's reset signal is likely all this script needs to
do. However, in some scenarios, this script may perform other actions. For
example, it may call out to some SoC- or board-specific vendor utility in order
to download the U-Boot binary directly into RAM and execute it. This would
-avoid the need for ``u-boot-test-flash1`` to actually write U-Boot to flash,
+avoid the need for ``u-boot-test-flash`` to actually write U-Boot to flash,
thus saving wear on the flash chip(s).
u-boot-test-release