This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Pau Espin Pedrol pespin at sysmocom.deHi, On 14/06/17 15:03, Sudhanthiradasan R wrote: > > 1)Just for the confirmation.. for the end-to-end testing with the current version of osmo-gsm-tester we can use only the sms suite? > aoip_sms should be working too. It's basically the same as "sms" suite but using the AoverIP version of OpenBSC which will soon deprecate current OsmoNITB platform. > 2)In the suites directory, I can see aoip_debug, aoip_sms, debug, netreg, sms suites. What are all the tests that I can do with these suits? Is there any documentation? You can find the latest manual with general documentation in [1]. Feel free to ask if something is not clear or missing. If you want to improve it, the sources of the manual can be found in [2], patches welcome. * debug: A few minimal tests used during development of osmo-gsm-tester. You may find interesting the "interactive.py" one, which let's you start a test and set-up all the network + modems, then wait in a cmdline prompt waiting for you so you can debug whatever is going on. * aoip_debug: Same as debug, but using AoIP * netreg: A pair of minimal tests which check that the modems (ofono_client.py) can automatically/manually register with the network. It's a subset of what sms.py test is doing, but it's nice to have when willing to specifically test the register part. * sms: Starts the network, starts and registers 2 ofono modems (MS), sends an SMS from one MS to the other and then check's the sms arrived correctly and that the content is correct. * aoip_sms: Same as sms, but using AoIP. > > 3)If we want to create new suites, is there any document to help us? > You can have an idea of the current roadmap but checking at the tasks listed in the issue tracker of the project [3]. If you have any specific interest feel free to add tickets there (check similar ones don't exist before doing so). Incoming patches are welcome too. To know how to write new tests, the best is to check existing tests (sms.py), and you can find the API exported and available for tests in [4]. We extend the API when we implement new features which we see are required for new tests. [1] http://ftp.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf [2] http://git.osmocom.org/osmo-gsm-manuals/tree/OsmoGSMTester [3] https://osmocom.org/projects/osmo-gsm-tester/issues [4] http://git.osmocom.org/osmo-gsm-tester/tree/src/osmo_gsm_tester/test.py -- - Pau Espin Pedrol <pespin at sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte