Commit Graph

155 Commits

Author SHA1 Message Date
Harald Welte 845d397c19 mgw_test: Use entire "control" section of testsuite
Change-Id: Id4121bd6974b58faaa8c471597708085ce14a192
2018-03-28 12:21:36 +02:00
Philipp Maier 41962f7bf5 ttcn3-bscc-test/osmo-bsc.cfg: Add TCH/H channels
The configuration of osmo-bsc currently only supports halfrate
traffic channels. In order to test assignments which contain
half rate codecs we also have to have halfrate channels available.

Change-Id: Ibcce03ab0c98545a1f316d88e1f3dd75e2ff65e1
Related: OS#3100
Related: OS#3095
2018-03-27 13:35:29 +02:00
Harald Welte 284a8816f2 add ttcn3-sip-test container
Change-Id: Ibfe2a2b47c266788d51e98d64bca7017caf19e29
2018-03-27 09:21:20 +02:00
Harald Welte b0bc0c237e add 'osmo-sip-master' Dockerfile
Change-Id: Ie9623df1b3181ddcfd868c14f0b05614853447b0
2018-03-27 08:24:48 +02:00
Harald Welte 6f786a7383 ttcn3-bsc-test: Enable all codecs on all BTSs
We now have TC_assignment_codec_ tests which assume that those
codecs are available.

Change-Id: I0ff19a4bc9bba5ff2de3b5d4c399b483e8ca097b
2018-03-22 18:30:08 +01:00
Neels Hofmeyr 116e442b2a fix ttcn3-bsc-test: BSC_Tests.cfg: set mp_test_ip
Allow the osmo-bsc-main docker container to reach the virtual MGW set up by the
ttcn3-bsc-tests.

The module parameter mp_test_ip sets the IP address at which the virtual
services are set up to listen for connections -- currently actually only the
virtual MGW. Set this to 172.18.2.203 instead of using the default 127.0.0.1.

This fixes the second half of the disconnect between BSC and virtual MGW in
this docker setup. The first half is Ib53f000ec7e717b14a3e5df6e803d3d0950b937f

Change-Id: I3038481ed0bba1084b63dc6a6d2ff6e970100890
2018-03-20 16:58:06 +01:00
Neels Hofmeyr 2f5a5b689c fix ttcn3-bsc-test: osmo-bsc.cfg: add mgw IP
The osmo-bsc-main docker container is run in a separate docker container and
cannot reach the virtual MGW set up by the ttcn3-bsc-tests.

From ttcn3-bsc-tests/jenkins.sh it is clear that the tests are run at IP
172.18.2.203. Add this as the 'mgw remote-ip' setting in
ttcn3-bsc-tests/osmo-bsc.cfg.

This fixes the first half of the disconnect between BSC and virtual MGW in this
docker setup. The second half is I3038481ed0bba1084b63dc6a6d2ff6e970100890.

Change-Id: Ib53f000ec7e717b14a3e5df6e803d3d0950b937f
2018-03-20 00:42:45 +01:00
Neels Hofmeyr a966cdfe4c debian-stretch-titan: add vim
When developing in the actual docker containers, vim is inexpendible.

Change-Id: I964e29c82ab9a1fb2a39845bc45a0d2cead56880
2018-03-19 14:12:43 +01:00
Harald Welte 32f13b23af ttcn3-bsc-test: Fix location of respawn.sh script 2018-03-19 07:47:10 +00:00
Harald Welte c90d07003c ttcn3-msc-test: Disable MM INFO
In the past, MM INFO transmission was broken, so the tests were
written without expecting it.  Now, the bug in osmo-msc has been
fixed.

With the config file enabling it, and the tests not expecting MM INFO,
a lot of them failed. Let's disable MM INFO for now until the tests
can deal with it
2018-03-18 21:38:43 +00:00
Harald Welte 3c34820699 ttcn3-msc-test: fix MNC/MCC to match MSC_Tests.ttcn
We recently introduced verification of the MCC/MNC, and the osmo-msc.cfg
MCC/MNC settings mis-matched those of MSC_Tests.ttcn resulting in lots
of test failures.
2018-03-18 17:06:39 +01:00
Harald Welte 2f5541b134 ttcn*test: use log_merge.sh to generate per-testcase merged logs 2018-03-18 13:33:39 +00:00
Harald Welte c99a78fc9e remove osmo-bts-omldummy container, it's now part of osmo-bts-master 2018-03-17 15:41:43 +00:00
Harald Welte e90ee9602b debian-stretch-titan: Use osmocom build of titan 6.3.x
Debian 9.0 ships with titan 6.1.0 which for some unknown reasons
causes segfaults in the C++ part when parsing CTRL messages and
according to TITAN project is not supported anymore anyway.

So let's use a 6.3.x build, or whatever is the highest version in
the network:osmocom:latest feed instead.
2018-03-16 17:41:44 +01:00
Harald Welte 76e59987b3 bts-test: Change logging to file so we get BTS/BSC logs as test result 2018-03-13 13:29:23 +00:00
Harald Welte f08dadbf5f Add *.control to the [EXECUTE] statement of all ttcn3 test suites
In osmo-ttcn3-hacks, we have removed the *.control from the *.default
files, so let's add it here in the config files.  You can now change
the tests to be executed by simply editing the config here.
2018-03-13 13:26:51 +00:00
Harald Welte a59c18da01 Add ttcn3-hlr-test container 2018-03-01 16:22:21 +00:00
Harald Welte c8158f9349 Add new 'osmo-hlr-master' container (for upcoming HLR tests) 2018-03-01 15:19:53 +00:00
Harald Welte c0da6a0e7a Add osmo-bts-test + dependencies 2018-03-01 15:19:49 +00:00
Neels Hofmeyr e707891fa8 fix osmo-bsc.cfg: drop no longer supported options 2018-02-23 15:09:29 +01:00
Philipp Maier 7453361fd0 ttcn3-bsc-test: enable A51 and A53 encryption
the BSC configuration currently only offers A50 (no) encryption.
Since the TTCN3 tests also cover assignment tests with encryption
and osmo-bsc now supports multiple cipher settings at a time this
setting should be extended accordingly.

- Also enable A51 and A53 encryption.
2018-02-19 22:16:12 +01:00
Pau Espin 3112a7b10a ggsn-test: Add missing DNSv6 addr in ggsn config
Test TC_pdp6_act_deact_pcodns checks the 2 DNS values against matched
configuration. If osmo-ggsn.cfg doesn't have a 2nd DNS configured, it
won't sent the related PCO in the response, and the test will fail.
2018-02-19 12:27:31 +01:00
Pau Espin bd41d24563 ggsn-test: Use ggsn local ip as announced DNS
This way the address is reachable for ggsn system and can route the
packet correctly.

This commit fixes runtime failures of
GGSN_Tests.TC_pdp4_act_deact_gtpu_access when running inside the
container, since that test uses the DNS address to attempt a ping and
waits for a response. If the address is non reachable/routable from
osmo-ggsn tun, then the packet is dropped by the kernel and no ping
response is sent back.
2018-02-19 12:12:06 +01:00
Pau Espin 56276f95fd jenkins.sh: Fix trailing whitespace 2018-02-19 12:03:39 +01:00
Pau Espin 51deedd956 *-test: jenkins.sh: Print junit output at the end 2018-02-19 11:59:00 +01:00
Harald Welte 24829d6f78 Add ttcn3-sgsn-test 2018-02-18 12:47:16 +01:00
Harald Welte 406b02090a osmo-sgsn-master: Use separate osmo-sgsn.git repository
Several months ago, osmo-sgsn received its own repository, and is no
longer contained in the openbsc.git.
2018-02-18 12:47:15 +01:00
Harald Welte 8e57c545ab ttcn3-msc-test: remove correct unix domain socket dir 2018-02-18 12:47:15 +01:00
Harald Welte b25e1ea779 ttcn3-msc-test: remove unix domain socket dir from both containers 2018-02-18 12:24:33 +01:00
Harald Welte 797fca544c Rename osmo_sgsn.cfg to osmo-sgsn.cfg
Since October 2017 the default config name no longer has an underscore
but a dash in the filename.  See osmo-sgsn.git Change-Id
If804da17a7481e79e000fe40ae0d9c4be9722e61
2018-02-18 12:09:35 +01:00
Harald Welte 226090762a ttcn3-msc-test: Remove unix domain socket before copying logs
jenkins otherwise fails when collecting the build artefacts
2018-02-16 20:05:55 +01:00
Harald Welte a564cfbd54 osmo-bts-master: Fix IP address for ttcn3-nitb-sysinfo
In d770629280 we introduced different
IP addresses for ttcn3-nitb-sysinfo, but forgot to update the BTS side
Address.
2018-02-15 07:53:14 +00:00
Harald Welte a36a6019c7 ttcn3-msc-test: Remove unix domain socket before copying logs
jenkins otherwise fails when collecting the build artefacts
2018-02-15 06:51:22 +00:00
Harald Welte 35d2cf3c0f ttcn3-nitb-sysinfo: Fix docker network usage
In d770629280 we broke the
ttcn3-nitb-sysinfo builds when switching to jenkins-common.sh

This commit fixes it.
2018-02-14 21:08:53 +00:00
Harald Welte 10305f2f8f ttcn3: Add OSMO_TTCN3_BRANCH build-time argument to build non-master branches 2018-02-14 21:57:39 +01:00
Harald Welte f14d94d26b ggsn-test: Switch to new common/shared config file structure
This requires I491819c8bad8efa45cee161ea6f47c3f97941a17 in
osmo-ttcn3-hacks
2018-02-14 21:57:01 +01:00
Harald Welte ad4f342b7d bumped to version 0.1.0-df5f204 2018-02-14 19:43:04 +00:00
Harald Welte df5f204dfa mgw: Use master branch, not accidential different branch 2018-02-14 19:35:13 +00:00
Harald Welte c1694826e4 Use new split config file + tcpdump support of osmo-ttcn3-hacks
This uses osmo-ttcn3-hacks Change-Id
I3db452e24e5238aa05254d903739c64d202e61db, which introduces
some shared/common config file as well as per-testcase pcap file
generation.
2018-02-14 19:06:46 +00:00
Harald Welte b7e818d8ab Make sure tcpdump is in debian-stretch-titan
this will enable us to automatically take pcap traces of test runs
2018-02-14 18:04:34 +00:00
Harald Welte d0fa0b0c41 ttcn3-msc-test: Update MSC_Tests.cfg (moduleparm changes) 2018-02-14 10:08:01 +01:00
Harald Welte edcda6b2f3 ttcn3-msc-test: Update osmo-msc.cfg to recent master (removed vty commands) 2018-02-14 09:06:23 +00:00
Harald Welte 5a76f11320 ttcn3-bsc-test: Fix log file name (osmo-bsc.log, not osmo-msc.log) 2018-02-14 09:06:03 +00:00
Harald Welte 675c76cfd5 ttcn3-bsc-test: Update config with recent changes (VTY, moduleparm change) 2018-02-14 09:05:35 +00:00
Harald Welte d770629280 jenkins: Add shared jenkins-common.sh
the common script contains some copy+pasted parts between the different
jobs.
2018-02-06 20:20:49 +00:00
Harald Welte bcc29baf39 jenkins: prefix all container names with $BUILD_TAG
... to make them unique and to allow for multiple tests run in parallel
without any clashes.
2018-02-06 19:57:24 +00:00
Harald Welte 9efd75aa44 bsc-test: omldummy now has an argument for number of TRX 2018-02-06 20:30:08 +01:00
Harald Welte 6e61e5a319 bsc/msc test: Make sure we create text log files
as we don't capture stderr on all *but* the tester container, let's
make sure we write log files from the BSC/MSC/STP containers
2018-02-06 20:22:39 +01:00
Harald Welte 213f8bd3f6 Fix ggsn test after last commit
We need a proper osmo-ggsn.cfg file with non-default IP addresses
2018-02-06 18:23:48 +00:00
Harald Welte facbb6575e move every 'test network' to its own IP address space
Ideally we would want to launch a group of containers with their own
private network segment and use the same static IP addresses in those
isolated networks.

The stupidity of docker is requiring unique IPv4 addresses even on
isolated (!) networks.  This means we have to manually give each of our
test setups a different subnet, and then we can at least run one
instance that test in parallel to at most one instance of each other
test.

If this weird reestriction about unique IPv4 addresses didn't exist,
we could start any number of test runs in parallel.
2018-02-06 19:08:45 +01:00