The idea behind this attribute is similar to the Features one in ofono: To provide an easy-to-use list of features that a modem supports. In osmo-gsm-tester this feature list can be used to create scenarios to act as a filter for modems. For instance, if an sms related feature must be tested, then a modem supporting sms features is required. This way only modems supporting that feature are going to be selected for that test when that scenario is used. We provide our own list instead of dynamically using it for two reasons: - Accessing the list from ofono means powering on + online the modem, which requires using the modem before resource resolution is done. - ofono may state that it has support for feature X, but it still doesn't have all features required by osmo-gsm-tester or there is a bug in some part of the feature which prevents it from being used for a specific test. Change-Id: I1634049f01859ae0310174892a96e204bb670bc1 |
||
---|---|---|
.. | ||
scenarios | ||
README.txt | ||
default-suites.conf | ||
defaults.conf | ||
paths.conf | ||
resources.conf |
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').