X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=test%2FREADME;h=4bc9ca3a6ae9de0e3ed6ff420c5edfe6027ad2c6;hb=5b4b680cfe29a67171ccbe439c66374cb31faca3;hp=6cfee05019147fd09ba29f1ad983b20432516563;hpb=07f4eadc99b365fa92114f19c02218ff39c45ed9;p=oweals%2Fu-boot.git

diff --git a/test/README b/test/README
index 6cfee05019..4bc9ca3a6a 100644
--- a/test/README
+++ b/test/README
@@ -10,10 +10,14 @@ Running tests
 
 To run most tests on sandbox, type this:
 
-    test/run
+    make check
 
 in the U-Boot directory. Note that only the pytest suite is run using this
-comment.
+command.
+
+Some tests take ages to run. To run just the quick ones, type this:
+
+    make qcheck
 
 
 Sandbox
@@ -29,7 +33,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:
 
@@ -46,7 +50,7 @@ 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 tools/tbot/README for more information.
+environment. See http://www.tbot.tools for more information.
 
 
 Ad-hoc tests
@@ -55,12 +59,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