summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2017-11-02 14:19:32 +0100
committerNeels Hofmeyr <neels@hofmeyr.de>2018-11-28 17:15:34 +0100
commitdc53c9c4665cd91975fcc8871f1c09f7c07fb2b1 (patch)
tree539a236c65824172c48301ac71f2500b3b20a396 /doc
parentc8cd1fa7c59ab0ea4f5f699206937374dd4201c2 (diff)
OsmoGSMTester: Improve Resource Resolution section content
Diffstat (limited to 'doc')
-rw-r--r--doc/manuals/chapters/intro.adoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manuals/chapters/intro.adoc b/doc/manuals/chapters/intro.adoc
index b405e1f..e2156df 100644
--- a/doc/manuals/chapters/intro.adoc
+++ b/doc/manuals/chapters/intro.adoc
@@ -202,12 +202,12 @@ wait(ms_mt.sms_was_received, sms)
=== Resource Resolution
-- A global configuration defines which hardware is connected to the
+- A global configuration 'resources.conf' defines which hardware is connected to the
osmo-gsm-tester main unit.
- Each suite contains a number of test scripts. The amount of resources a test
may use is defined by the test suite's 'suite.conf'.
- Which specific modems, BTS models, NITB IP addresses etc. are made available
- to a test run is typically determined by a combination of scenario
+ to a test run is typically determined by 'suite.conf' and a combination of scenario
configurations -- or picked automatically if not.
[[resources_conf_example]]