b0ebcbcf10
this refactor no longer enforces blocking operation of the process. Instead it returns the process object to the caller who can now run either proc.launch() for non-blocking operation or proc.launch_sync() for blocking mode. The non-block mode allos doing other stuff in the background, for example controlling the rfemu while running a ping. Change-Id: Ia6372e55a8829f722e40db537d9dfd63a94d1be9 |
||
---|---|---|
.. | ||
scenarios | ||
suites | ||
ttcn3 | ||
README.md | ||
default-suites.conf | ||
defaults.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').