osmo-gsm-tester

History

Pau Espin 31b7f0f9de resources.conf: EC20 doesn't support SupplementaryServices As the interface never appears, tests using the modem fail because we wait for all the interfaces to be available based on the features attribute. Change-Id: I68fcf2b9083966ad42940e1629abe2a1a6b74095		2017-12-05 18:26:06 +01:00
..
scenarios	Add features attribute to modems	2017-09-16 21:59:44 +02:00
README.txt	put the example suite in /example, not /selftest/real_suite	2017-05-04 16:42:50 +02:00
default-suites.conf	default-suites.conf: Add gprs suite	2017-12-05 15:06:53 +01:00
defaults.conf	osmo-bsc: Remove authentication cmd from config	2017-11-29 14:31:32 +01:00
paths.conf	paths: have one common parent dir /var/tmp/osmo-gsm-tester	2017-05-11 17:39:02 +02:00
resources.conf	resources.conf: EC20 doesn't support SupplementaryServices	2017-12-05 18:26:06 +01:00

README.txt

This a real gsm test suite configured and ready to use.
The only thing missing is a trial dir containing binaries.

You can point osmo-gsm-tester.py at this config using the OSMO_GSM_TESTER_CONF
environment variable:

    export OSMO_GSM_TESTER_CONF="$PWD"

When there is no OSMO_GSM_TESTER_CONF set, osmo-gsm-tester will instead look
for conf files in several locations like ~/.config/osmo-gsm-tester,
/usr/local/etc/osmo-gsm-tester, /etc/osmo-gsm-tester.

If you have your trial with binary tar archives in ~/my_trial
you can run the suite for example like this:

    osmo-gsm-tester.py ~/my_trial

Specifically, from this dir:

    OSMO_GSM_TESTER_CONF="$PWD" ../src/osmo-gsm-tester.py ~/my_trial

Alternatively you can setup this example as permanent config using something
like:

    mkdir -p ~/.config
    ln -s "$PWD" ~/.config/osmo-gsm-tester

A ./state dir will be created to store the current osmo-gsm-tester state. If
you prefer not to write to $PWD, set up an own configuration pointing at a
different path (see paths.conf: 'state_dir').