Since -latest was updated to newer releases, there's no need to change
the values of these params. Furthermore, they will be completely dropped soon.
Change-Id: I6121b435c5b984eab64d953e9d3f26eecc0e7bc5
Related: OS#5042
Default is MNCCv7 since osmo-ttcn3-hacks.git
I5448ff931ec33f24f4837a51376f1703fe97683b, but latest tagged version of
osmo-msc only supports MNCCv6.
Change-Id: Iaac2f5453214dfcf6efd070f6ea1212a7833eb1b
module param mp_enable_osmux_test is dropped in osmo-ttcn3-hacks.git
I8bc0551ec91a5fd8ea2f291a1e16a06a739c7a75.
module param mp_enable_crashing_tests is introduced in
osmo-ttcn3-hacks.git I46f1066323e19dfe708402a8c9c68e257f62751c.
Change-Id: I22bb43ba6d15eabcc731a2c3ef7aabc4f250d508
As of osmo-ttcn3-hacks.git Change-Id I4976d9bb1f07c8ab4ffa02848414f8ddd1bdfd3f
the test suite expects the MSC to send a CommonID to the BSC. As
older/existing tagged osmo-msc don't do that, we needt odisable that
check when verifying 'latest'.
Change-Id: If2e4cc41cb7b5758a78d694d62b34390a08e6387
Related: OS#2969
When introducing IPv6 support, we map the third digit of the IPv4
address (X) to the 6th byte of an IPv6 prefix "fd02:db8:X::/64"
However, the docker daemon seems to use "fd02:db8:1::/64" internally
for its default network, so creating a docker network with the same
IP address is failing.
Let's move the MSC test suite to another sub-net (1->20) to avoid
related problems.
Change-Id: I9c5f9b96d5523eae09f3f2e6c813e9e0d047f9ab
Latest tagged version of osmo-msc doesn't support "osmux on/off" VTY
commands, so we have to enable osmux use on that version to avoid most
TTCN3 tests failing during set up phase.
Depends: osmo-ttcn3-hacks.git I53d58b2d905905ebf1df322d0389b3715a48212f
Change-Id: I6b3be3981978661de2fa90be130f6f1811a3d1f9
The new IuCS related tests have been added as 'MSC_Tests_Iu'
module to take advantage of the hierarchical display format in the
Jenkins tests results analyzer. Let's execute them.
Change-Id: I80ccfce4874d14039bbcb273c3b450db2a7780dd
We need to update the MSC_Tests.cfg as well as the osmo-stp.cfg
to provsion a virtual RNC link. As the new RNC uses routing key 2,
we shift the MSC routing key to 3.
Change-Id: I10a249b1a851436fd3c20face6ccc94b304bd3e4
After merging Change-Id: Ie844c4de62e0ef5d5c4c366185968211a7f6d676
in osmo-ttcn3-hacks, the module parameters for BSSAP configuration
require one extra argument.
Change-Id: I2a0011bc6f7bdf013005d1ea36da591673344eed
Related: OS#2544
The MSC_Tests.ttcn testsuite is now able to present multiple BSC
to the MSC (IUT). This change requires the configuration files
of osmo-stp and of the testsuite to be changed.
- update MSC_Tests.cfg to present up to two BSCs to the MSC
- update osmo-stp.cfg to support the additional connection
from the testsuite
Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2
Depends: osmo-ttcn3-hacks I52a4c8118828c1605cf672889982f987568ad17d
Related: OS#1609
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.
This uses osmo-ttcn3-hacks Change-Id
I3db452e24e5238aa05254d903739c64d202e61db, which introduces
some shared/common config file as well as per-testcase pcap file
generation.
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.
Pau Espin
Harald Welte
Neels Hofmeyr
Philipp Maier