osmo-gsm-tester

History

Pau Espin a52855614a ttcn3: Allow remote hosts (sysmobts) to access RSL srv inside TTCN3 docker And extra IP address is required/requested on the docker host because the BSC handling the OML instance is binding to it's address, so we cannot ask docker to use that one because it fails binding to it. Change-Id: I734fba91db535d7b183ddc7f51d324a6cd2eaf6f		2018-10-15 17:59:31 +02:00
..
scenarios	ttcn3: Support running tests without PCU socket avail	2018-10-15 17:55:12 +02:00
suites/ttcn3_bts_tests	ttcn3: Allow remote hosts (sysmobts) to access RSL srv inside TTCN3 docker	2018-10-15 17:59:31 +02:00
README.txt	Add ttcn3-bts-test env	2018-07-25 16:38:30 +02:00
default-suites.conf	ttcn3: Allow remote hosts (sysmobts) to access RSL srv inside TTCN3 docker	2018-10-15 17:59:31 +02:00
defaults.conf	Add ttcn3-bts-test env	2018-07-25 16:38:30 +02:00
jenkins-run.sh	Add ttcn3-bts-test env	2018-07-25 16:38:30 +02:00
paths.conf	Add ttcn3-bts-test env	2018-07-25 16:38:30 +02:00
resources.conf.prod	Add ttcn3-bts-test env	2018-07-25 16:38:30 +02:00
resources.conf.rnd	Add ttcn3-bts-test env	2018-07-25 16:38:30 +02:00

README.txt

This directory contains a set of scripts and osmo-gsm-tester testsuites to run
osmo-ttcn3-hacks.git BTS_tests.ttcn (https://git.osmocom.org/osmo-ttcn3-hacks/tree/bts).

The idea is to set up automatically the following components:
TTCN3 <-> osmocon (osmocom-bb) <-> motorola C123 <-> RF network <-> BTS_TO_TEST <-> TTCN3 + osmo-bsc

* A jenkins job builds a docker image containing a built BTS_tests TTCN testsuite.
* Another jenkins job retrieves the artifacts from osmo-gsm-tester-build jobs
  plus one for required osmocon binary. This job then calls osmo-gsm-tester/ttcn3/jenkins-run.sh, which will:
** Pull the above mentioned docker image containing BTS_Tests.
** Start osmo-gsm-tester with OSMO_GSM_TESTER_OPTS=osmo-gsm-tester/ttcn3/paths.conf,
   that contains mostly same stuff as regular osmo-gsm-tester jobs, but with a
   different testsuite containing 1 test "ttcn3_bts_tests.py".
** The test "ttcn3_bts_tests.py" does the following:
*** Start and manage all osmocom required components to run BTS_Tests: osmo-bts, osmo-bsc, osmocon, etc.
*** Generate the BTS_Tests.cfg required by BTS_Tests from a template to adapt to dynamic bits set by osmo-gsm-tester.
*** Launch script osmo-gsm-tester/ttcn3/suites/ttcn3_bts_tests/scripts/run_ttcn3_docker.sh with parameters and wait for it to finish.
    This script will start and manage the lifecycle of the docker container running BTS_Tests

See OS#3155 for more information regarding this topic.