Feature #2199
closedFeature #2193: write osmo-gsm-tester test cases and extend tester API
osmo-gsm-tester: provide API to reflect whether an osmo-nitb has started successfully
0%
Description
The mo_mt_sms.py test has a sleep(1) to wait for the osmo-nitb to startup.
The intention is to give it a moment to parse the config file and fail immediately in case startup failed.
Technically, this is not necessary at all. The tester would notice by itself if the nitb process has terminated prematurely. Nevertheless it is good to have API to wait for the osmo-nitb to state some particular message on stdout or the log that reflects that the config has been read and all ports are listening. Add such API (reading stdout/stderr? using CTRL?) and use this in the mo_mt_sms.py test to replace the sleep(1).
This is low priority, we can just remove the sleep(1) and 'assert nitb.running()' lines, relying on the standard process polling, without affecting the test results.
