test: Fix typos and tidy up
Fix review comments that were missed at the time. Also explain why we need
to regenerate the device tree for each test.
Reported-by: Teddy Reed <teddy.reed@gmail.com>
Suggested-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
Fixes: f6349c3c (test: Add a README)
diff --git a/test/README b/test/README
index ee55972..1142e9c 100644
--- a/test/README
+++ b/test/README
@@ -13,7 +13,7 @@
test/run
in the U-Boot directory. Note that only the pytest suite is run using this
-comment.
+command.
Sandbox
@@ -29,7 +29,7 @@
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:
@@ -55,11 +55,11 @@
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)
-The above should be converted to run as part of the pytest suite.
+TODO: Move these into pytest.
When to write tests