cellular-infrastructure
/
osmo-gsm-tester
mirror of https://gerrit.osmocom.org/osmo-gsm-tester
9
0
Fork 0
Code Issues Releases Wiki Activity
Osmocom GSM Tester, jenkins integrated GSM hardware testing https://osmocom.org/projects/osmo-gsm-tester
1,103 Commits 25 Branches 1 Tag 13 MiB
Python 94.4%
Shell 4.4%
Lua 1.1%
Go to file
Neels Hofmeyr 9596b210c5 add test.report_fragment() 
Allow enriching the junit output with arbitrary subtasks within a test.

The current aim is, for handover tests, to not just show that a test
failed, but to show exactly which steps worked and which didn't, e.g.:

 handover.py/01_bts0_started PASSED
 handover.py/02.1_ms0_attach PASSED
 handover.py/02.2_ms1_attach PASSED
 handover.py/02.3_subscribed_in_msc PASSED
 handover.py/03_call_established PASSED
 handover.py/04.1_bts1_started FAILED

In this case it is immediately obvious from looking at the jenkins
results analyzer that bts1 is the cause of the test failure, and it is
visible which parts of the test are flaky, over time.

First user Will be the upcoming handover_2G suite, in
I0b2671304165a1aaae2b386af46fbd8b098e3bd8.

Change-Id: I4ca9100b6f8db24d1f7e0a09b3b7ba88b8ae3b59
 		2020-12-11 00:19:13 +01:00
contrib contrib: Disable libmnl dependency cross-compiling osmo-bts 2020-12-08 12:02:07 +01:00
doc resource: Support waiting for reserved resources until available 2020-11-11 11:38:35 +00:00
selftest add test.report_fragment() 2020-12-11 00:19:13 +01:00
src add test.report_fragment() 2020-12-11 00:19:13 +01:00
sysmocom configure fixed ARFCN per bts 2020-12-11 00:19:13 +01:00
utils Copy gnuradio zmq broker at runtime 2020-10-22 11:28:26 +02:00
.gitignore Support identifying different tgz files based on run_label attribute 2020-05-28 13:13:05 +00:00
.gitreview Add git-review config 2017-12-15 11:29:21 +00:00
COPYING Add GPLv3 license text to repository 2017-06-03 14:23:51 +00:00
Makefile Move update_version.sh to contrib/ 2020-05-12 14:07:36 +02:00
README.md Rework README file 2020-05-05 19:25:33 +02:00

README.md

About Osmo-GSM-Tester

Osmo-GSM-Tester is a software to run automated tests on real hardware, initially foremost to verify that ongoing Osmocom software development continues to work with various BTS models, while being flexibly configurable and extendable to work for other technologies, setups and projects. It can nowadays also be used to run 4G networks with components from different providers.

Find Osmo-GSM-Tester issue tracker and wiki online at https://osmocom.org/projects/osmo-gsm-tester

Simple configuration setups can be found under doc/examples/ directory. A Osmocom's public Osmo-Gsm-Tester configuration setup is also maintained here under sysmocom/ as a reference for others.

Ansible scripts to set up hosts to be used as Osmo-GSM-Tester Main Units or/and Slave Units on the above mentioned setup can be found at https://git.osmocom.org/osmo-ci/tree/ansible, which actually install sample system configuration files from utils/ directory in this same repository.

A sample Docker setup is also maintained publicly at https://git.osmocom.org/docker-playground/tree/osmo-gsm-tester.

For the complete documentation, please refer to Osmo-GSM-Tester User manual, available in sources under doc/manuals/ under this same repository, and prebuilt in pdf form at http://ftp.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf