osmith submitted this change.

Approvals:
  pespin: Looks good to me, approved
  Jenkins Builder: Verified
  fixeria: Looks good to me, but someone else must approve

testenv/README: update

Point at ./testenv.py -h and describe that everything runs in 1
container with --podman.

Change-Id: Ie9eee8cf14ba2069c1cd5bd6ab703f3f6ccdc100
---
M _testenv/README.md
1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/_testenv/README.md b/_testenv/README.md
index 2c5a181..5eee2d2 100644
--- a/_testenv/README.md
+++ b/_testenv/README.md
@@ -1,6 +1,24 @@
 # testenv
 
-Build everything needed for running Osmocom TTCN-3 testsuites and execute them.
+Testenv builds and runs a testsuite and all the components it tests (usually
+one or more Osmocom programs). See `./testenv.py -h` for command-line usage
+help.
+
+Example for running the `mgw` testsuite:
+```
+$ ./testenv.py run mgw
+```
+
+## Virtualization
+
+By default testenv does everything directly on the host, without using a
+container. The `--podman` parameter can be used to build and run everything in
+a container instead.
+
+When passing `--podman`, then just one container is used to build and run
+everything. The container is the same, no matter which testsuite gets executed.
+Additional packages get installed after starting the container, with a package
+cache mounted to avoid unnecessary downloads.
 
 ## testenv.cfg

To view, visit change 37886. To unsubscribe, or for help writing mail filters, visit settings.