Pali Rohár 1ce0e1cbcc Nokia RX-51: Add test for U-Boot serial console 3 년 전
..
cmd 2c02152a8e setexpr: Add support for strings 3 년 전
dm 15daa4860b dm: core: add a function to decode display timings 3 년 전
env 96434a76fd env: Allow returning errors from hdelete_r() 3 년 전
fs 84f0415201 Consistently use nproc for counting the CPUs 4 년 전
image 280fafff16 test: Update test-imagetools.sh to match new syntax 5 년 전
lib fbc33df13c test: Add a test for getopt 3 년 전
log 89723b9494 test: Add a test for log filter-* 3 년 전
optee f7ae49fc4f common: Drop log.h from common header 4 년 전
overlay f7ae49fc4f common: Drop log.h from common header 4 년 전
py acfb5308f5 sandbox: Drop unnecessary test node 3 년 전
stdint dee37fc99d Remove <inttypes.h> includes and PRI* usages in printf() entirely 5 년 전
trace 83d290c56f SPDX: Convert all of our single license tags to Linux Kernel style 6 년 전
Kconfig de429d7b09 test: linking test/compression.c fails 3 년 전
Makefile f158ba15ee bootm: Add tests for fixup_silent_linux() 3 년 전
README 499fde5c23 test: Add a 'make qcheck' target for quicker testing 5 년 전
bloblist.c 4c1497e776 bloblist: Allow custom alignment for blobs 3 년 전
bootm.c 51bb33846a bootm: Support string substitution in bootargs 3 년 전
cmd_ut.c f158ba15ee bootm: Add tests for fixup_silent_linux() 3 년 전
command_ut.c f7ae49fc4f common: Drop log.h from common header 4 년 전
common.sh 84f0415201 Consistently use nproc for counting the CPUs 4 년 전
compression.c f91f366bd5 test: Use ut_asserteq_mem() where possible 4 년 전
nokia_rx51_test.sh 1ce0e1cbcc Nokia RX-51: Add test for U-Boot serial console 3 년 전
print_ut.c f7ae49fc4f common: Drop log.h from common header 4 년 전
run 7b51bf770a test: Run SPL unit tests 3 년 전
str_ut.c 0914011310 command: Remove the cmd_tbl_t typedef 4 년 전
time_ut.c c05ed00afb common: Drop linux/delay.h from common header 4 년 전
unicode_ut.c fe179d7fb5 efi_loader: Add size checks to efi_create_indexed_name() 3 년 전
ut.c 33d7edfd5f test: Add a way to check part of a console line or skip it 3 년 전

README

Testing in U-Boot
=================

U-Boot has a large amount of code. This file describes how this code is
tested and what tests you should write when adding a new feature.


Running tests
-------------

To run most tests on sandbox, type this:

make check

in the U-Boot directory. Note that only the pytest suite is run using this
command.

Some tests take ages to run. To run just the quick ones, type this:

make qcheck


Sandbox
-------
U-Boot can be built as a user-space application (e.g. for Linux). This
allows test to be executed without needing target hardware. The 'sandbox'
target provides this feature and it is widely used in tests.


Pytest Suite
------------

Many tests are available using the pytest suite, in test/py. This can run
either on sandbox or on real hardware. It relies on the U-Boot console to
inject test commands and check the result. It is slower to run than C code,
but provides the ability to unify lots of tests and summarise their results.

You can run the tests on sandbox with:

./test/py/test.py --bd sandbox --build

This will produce HTML output in build-sandbox/test-log.html

See test/py/README.md for more information about the pytest suite.


tbot
----

Tbot provides a way to execute tests on target hardware. It is intended for
trying out both U-Boot and Linux (and potentially other software) on a
number of boards automatically. It can be used to create a continuous test
environment. See http://www.tbot.tools for more information.


Ad-hoc tests
------------

There are several ad-hoc tests which run outside the pytest environment:

test/fs - File system test (shell script)
test/image - FIT and legacy image tests (shell script and Python)
test/stdint - A test that stdint.h can be used in U-Boot (shell script)
trace - Test for the tracing feature (shell script)

TODO: Move these into pytest.


When to write tests
-------------------

If you add code to U-Boot without a test you are taking a risk. Even if you
perform thorough manual testing at the time of submission, it may break when
future changes are made to U-Boot. It may even break when applied to mainline,
if other changes interact with it. A good mindset is that untested code
probably doesn't work and should be deleted.

You can assume that the Pytest suite will be run before patches are accepted
to mainline, so this provides protection against future breakage.

On the other hand there is quite a bit of code that is not covered with tests,
or is covered sparingly. So here are some suggestions:

- If you are adding a new uclass, add a sandbox driver and a test that uses it
- If you are modifying code covered by an existing test, add a new test case
to cover your changes
- If the code you are modifying has not tests, consider writing one. Even a
very basic test is useful, and may be picked up and enhanced by others. It
is much easier to add onto a test - writing a new large test can seem
daunting to most contributors.


Future work
-----------

Converting existing shell scripts into pytest tests.