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,098 Commits 25 Branches 1 Tag 13 MiB
Python 94.4%
Shell 4.4%
Lua 1.1%
Go to file
Neels Hofmeyr 081e89f477 fix: line nr in test name in wrong places 
test.Test() overrides name() in order to provide source line number
information. However, overriding name() is the wrong place for that, as
name() is also often used for identifying an object - when listing the
tests of a suite, the line number should not appear in the test name.
For example, the line number sometimes ends up in the test results in
jenkins, making 'foo.py' and 'foo.py:23' two distinct report items.

Instead, add a separate function Origin.src() that defaults to name(),
but specific classes can override src() if they wish to provide more
detailed information with the object name.

Override src() in Test, not name().

Use src() in backtraces.

The suite_test.ok shows that the backtracing in the log remains
unchanged, but the place where the test name is printed is corrected:
   I am 'test_suite' / 'hello_world.py:23'
becomes
   I am 'test_suite' / 'hello_world.py'
(Notice that "[LINENR]" in suite_test.ok is a masking of an actual
number, done within the selftest suite)

Change-Id: I0c4698fa2b3db3de777d8b6dcdcee84e433c62b7
 		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 fix: line nr in test name in wrong places 2020-12-11 00:19:13 +01:00
src fix: line nr in test name in wrong places 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