osmith has uploaded this change for review.

View Change

README: explain how to run testsuites manually

As the testsuites are now in the _build directory, running them might
not be as obvious. Add an example to the README. While at it, explain a
bit more what the testenv script does and where one can read more about
it.

Change-Id: I1ee9319ada889a8dd43cfb32776dc1a8ae12d607
---
M README.md
1 file changed, 20 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/31/40131/1

diff --git a/README.md b/README.md
index 94bc73a..b694fd3 100644
--- a/README.md
+++ b/README.md
@@ -19,6 +19,26 @@
 $ ./testenv.py run mgw
 ```
 
+This will build the mgw testsuite from source, as well as osmo-mgw and all its
+dependencies and then run the testsuite against it. The Osmocom sources will be
+cloned if they don't exist in a sibling directory to osmo-ttcn3-hacks. It is
+also possible to use the Osmocom binary packages with this and running
+everything inside a podman container. See `./testenv.py -h` and
+`_testenv/README.md` for more information.
+
+### Manually
+
+Alternatively you can build and run the testsuite yourself, e.g.:
+
+```
+$ make mgw
+$ cd mgw
+$ ../start-testsuite.sh ../_build/mgw/MGCP_Test MGCP_Test.cfg
+```
+
+Make sure that all components that the testsuite requires are running
+(`osmo-mgw` in this example).
+
 ## Continuous Integration
 
 The individual tests suites are executed against different versions of

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