dm: test: Add support for running tests with livetree

[people/ms/u-boot.git] / test / README

diff --git a/test/README b/test/README
index dfd83d631cc496cbbf19030aeb7a20a95b150030..1142e9ca996c9e5b5641fbef26e9c83a1c40a645 100644 (file)
--- a/test/README
+++ b/test/README
@@ -5,6 +5,17 @@ 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:
+
+    test/run
+
+in the U-Boot directory. Note that only the pytest suite is run using this
+command.
+
+
 Sandbox
 -------
 U-Boot can be built as a user-space application (e.g. for Linux). This
@@ -18,7 +29,7 @@ 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 test and summarise their results.
+but provides the ability to unify lots of tests and summarise their results.
 
 You can run the tests on sandbox with:
 
@@ -44,12 +55,11 @@ 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 lagacy image tests (shell script and Python)
+   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)
-   vboot       - Test for verified boot (shell script)
 
-The above should be converted to run as part of the pytest suite.
+TODO: Move these into pytest.
 
 
 When to write tests