osmo-gsm-tester/example
Pau Espin e0a3d3eeed default-suites.confg: Add suites to test LimeNet-micro
Change-Id: I7f774e7bf6539c5afd1d3e35da765ba8d702fdb7
2019-11-26 14:39:36 +01:00
..
scenarios bts_osmotrx: Add support to run osmo-trx on LimeNet-micro 2019-11-26 14:33:11 +01: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.confg: Add suites to test LimeNet-micro 2019-11-26 14:39:36 +01:00
defaults.conf Integrate osmo-{bts,pcu}-oc2g 2019-03-27 13:50:41 +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.prod bts_osmotrx: Add support to run osmo-trx on LimeNet-micro 2019-11-26 14:33:11 +01:00
resources.conf.rnd resources.conf: Mark osmo-bts-trx as supporting a5/3 2019-11-26 14:19:37 +01:00
resources.conf.virtual nitb_netreg_mass: Provide 100 subscribers 2019-03-07 10:05:48 +00: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').