tests,misc: update TESTING.md documentation
* Documentation was assuming only tests in tests/test-progs were run.
This is not true anymore since we are running linux-boot for arm
which doesn't have a directory inside test-progs and because it
is now possible to explicitly specify the bin directory
Signed-off-by: Giacomo Travaglini <email@example.com>
Reviewed-by: Ciro Santilli <firstname.lastname@example.org>
Reviewed-by: Jason Lowe-Power <email@example.com>
Maintainer: Jason Lowe-Power <firstname.lastname@example.org>
Tested-by: kokoro <email@example.com>
diff --git a/TESTING.md b/TESTING.md
index cf160e6..6670621 100644
@@ -197,16 +197,23 @@
## Binary test applications
-The code for test binaries that are run in the gem5 guest during testing are
-found in `tests/test-progs`.
+The code for some test binaries that are run in the gem5 guest during
+testing can be found in `tests/test-progs`.
There's one directory per test application.
The source code is under the `source` directory.
You may have a `bin` directory as well.
The `bin` directory is automatically created when running the test case that
-uses the test binary. The binary is downloaded from the gem5 servers the first
+uses the test binary.
+This is not the case when a test is run via the --bin-path option.
+In that scenario a bin directory will be created in the selected path
+rather than in `tests/test-progs`.
+The binary is downloaded from the gem5 servers the first
time it is referenced by a test.
+Some other tests (like Linux-boot) don't have sources inside gem5 and
+are simply downloaded from gem5 servers.
## Updating the test binaries
The test infrastructure should check with the gem5 servers to ensure you have