osmo-gsm-tester

History

Pau Espin 2e5a89e307 ttcn3: Increase TTCN3 IPA UP to have sysmobts tests working It was spotted that most TTCN3 tests run against sysmobts fail because of following error: BTS_Tests.ttcn:643 Test case TC_chan_act_react finished. Verdict: fail reason: "BTS_Tests.ttcn:399 : Timeout waiting for ASP_IPA_EVENT_UP" Looking carefully at the logs and pcap files, it was seen that usually sysmobts tries to connect around 1 second after the TTCN3 tests decides it's enough. Current timeout was default of 15 seconds. Let's set it to 30 seconds. While at it, also set mp_ipa_up_delay, as initially set to 3 seconds in osmo-ttcn3-hacks.git d95f340a01fe7e9fe59f02b6ec4f9d018feb8c75 having physical tests in mind. Change-Id: I25c0a49851865291c6251556aff139961c3d4166		2019-07-25 15:05:16 +02:00
..
scenarios	ttcn3: Enable tests against O2CG	2019-03-27 13:50:41 +01:00
suites/ttcn3_bts_tests	ttcn3: Increase TTCN3 IPA UP to have sysmobts tests working	2019-07-25 15:05:16 +02:00
README.txt	Add ttcn3-bts-test env	2018-07-25 16:38:30 +02:00
default-suites.conf	ttcn3: Enable tests against O2CG	2019-03-27 13:50:41 +01: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.