Pau Espin
85968eef35
Since recently, the ttcn3-bts-test image is available in the osmocom registry. Let's use that one instead of the sysmocom one. The imaqge is built and pushed to the registry regularly by osmocom jenkins job registry-rebuild-upload-ttcn3-bts-tests (see osmo-ci.git/jobs/registry-rebuild-upload-titan.yml). Related: SYS#5765 Change-Id: I6de9719830290aa7f3ca80a6080ed37f107bdc16 |
||
---|---|---|
.. | ||
scenarios | ||
suites | ||
ttcn3 | ||
README.md | ||
default-suites.conf | ||
defaults.conf | ||
handover-suites.conf | ||
main.conf | ||
resources.conf.prod | ||
resources.conf.rnd | ||
resources.conf.virtual |
README.md
This a real 2G 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 '-c $DIR/main.conf' command line argument, where DIR is the directory path where this README file resides.
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 -c $DIR/main.conf ~/my_trial
Alternatively you can setup this example as default config for your user by doing something like:
mkdir -p ~/.config
ln -s "$DIR" ~/.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 $DIR, set up an own configuration pointing at a different path (see main.conf: 'state_dir').