Project

General

Profile

Titan TTCN3 Testsuites » History » Version 32

laforge, 04/21/2019 10:38 AM
add note on libfftranscode

1 2 laforge
{{>toc}}
2
3 1 laforge
h1. Osmocom Titan TTCN3 Testsuites
4
5 14 osmith
In 2017, Osmocom started to create extensive tests suites for the Cellular Network Infrastructure elements.  Those suites are written in the [[TTCN-3]] programming language and use the compiler and executor of the [[Eclipse_TITAN]] project. There are special cases, but in general, the idea is to test one component (e.g. @osmo-mgw@) independently.
6 2 laforge
7
h2. Source Code / Patches
8
9
The source code of our test suites lives in the @osmo-ttcn3-hacks@ repository
10
* cgit web interface: http://git.osmocom.org/osmo-ttcn3-hacks/
11
* clone: @git clone git://git.osmocom.org/osmo-ttcn3-hacks@
12
* patch review: https://gerrit.osmocom.org/#/q/project:osmo-ttcn3-hacks
13
14
We're following the [[Gerrit]] process for patch review.
15
16 32 laforge
h2. Proprietary APER<->BER transcoding library for Iu tests
17
18
As TITAN can only generate and parse ASN.1 BER encoding, but the Iu-CS, Iu-PS and Iuh interfaces are using APER encoding, sysmocom is providing a proprietary transcoding library called libfftranscode.  Debian9 amd64 packages are available from https://ftp.osmocom.org/binaries/libfftranscode/
19
20
We don't like to depend on proprietary software, but given that there is no FOSS ASN.1 compiler that can parse all ASN.1 constructs of the RANAP/RUA/HNBAP specs *and* parse + generate both BER and APER, this is the lesser evil.  Note that the dependency to this proprietary library is only required for the TTCN3 test suite and not a runtime dependency of any of the Osmocom programs itself.
21
22 2 laforge
h2. Test Suites
23
24
|_.Implementation under Test|_.Testsuite|_.Jenkins|
25
|bsc-nat|http://git.osmocom.org/osmo-ttcn3-hacks/tree/bsc-nat|-|
26
|[[OsmoBSC:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/bsc|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/|
27
|[[OsmoBTS:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/bts|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/|
28
|[[OpenGGSN:OsmoGGSN]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/ggsn_tests|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-ggsn-test/|
29
|[[OsmoHLR:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/hlr|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-hlr-test/|
30
|[[OsmoMGW:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/mgw|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-mgw-test/|
31
|[[OsmoMSC:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/msc|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-msc-test/|
32
|[[OsmoPCU:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/pcu|-|
33
|[[OsmoSGSN:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/sgsn|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-sgsn-test/|
34
|[[osmo-sip-connector:]]|http://git.osmocom.org/osmo-ttcn3-hacks/tree/sip|https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-sip-test/|
35
36
h2. Running a testsuite
37
38
You have multiple options on how to execute a test suite.
39
40
h3. Running test suite in the dockerized environment
41 1 laforge
42 4 osmith
This is the much easier way to run the test suite.  No manual configuration of Osmocom programs or the test suite are required.  Both the Osmocom program (Implementation Under Test) as well as the test suite are packaged as docker containers, which are then executed next to each other using a docker network with the "right" addresses between IUT and testsuite.
43 2 laforge
44
Also, using this setup you will be guaranteed to run in the exact same environment as the automatically-executed tests on jenkins.osmocom.org, i.e. your results should be exactly identical, without any differences introduced by your runtime environment, whether specific library versions or intentional or inadvertent configuration differences.
45
46 10 osmith
h4. Installing docker
47 1 laforge
48 10 osmith
Make sure you have "*docker-ce*":https://docs.docker.com/install/#supported-platforms installed (not to be confused with the possibly outdated version that may be shipped in your distribution's repositories). Check that the version string contains <code>-ce</code> as follows:
49
50
<pre>
51
$ docker -v
52
Docker version 18.06.1-ce, build e68fc7a
53
</pre>
54
55
56 11 osmith
Next, add yourself to the <code>docker</code> group, log off and on again, and verify that you can use docker with your user:
57 10 osmith
58
<pre>
59
$ docker info
60
</pre>
61
62
h4. Cloning docker-playground
63
64 12 osmith
Osmocom related containers are stored in the "@docker-playground@":https://git.osmocom.org/docker-playground/ git repository.
65 5 osmith
66
<pre>
67
$ git clone git://git.osmocom.org/docker-playground
68
$ cd docker-playground
69 1 laforge
</pre>
70 6 osmith
71 1 laforge
h4. Running a testsuite
72
73 25 osmith
All testsuite folders start with @ttcn3@ or @nplab@. Run the following to build/update all required containers and start a specific testsuite:
74 24 osmith
75 1 laforge
<pre>
76 24 osmith
$ cd ttcn3-mgw-test
77
$ ./jenkins.sh
78 1 laforge
</pre>
79
80 24 osmith
Environment variables:
81
* @IMAGE_SUFFIX@: the version of the Osmocom stack to run the testsuite against. Default is `master`, set this to `latest` to test the last stable releases.
82 29 osmith
* @OSMO_TTCN3_BRANCH@: "osmo-ttcn3-hacks.git":https://git.osmocom.org/osmo-ttcn3-hacks/ branch, which will be used when building a `ttcn3-*` docker image. Defaults to `master`.
83 24 osmith
* @NO_DOCKER_IMAGE_BUILD@: when set to @1@, it won't try to update the containers (see "README.md":https://git.osmocom.org/docker-playground/tree/README.md)
84
85 6 osmith
The @jenkins.sh@ script will make sure to
86 24 osmith
* create the needed docker network(s)
87 6 osmith
* run all the required containers (IUT, helpers, testsuite)
88
* shut them down after test suite execution
89
* collect the log files after execution, @/tmp/logs@ will contain them
90
91 2 laforge
h4. Running only a sub-set of the test cases
92
93 20 osmith
See running the testsuite outside of Docker for reference (below).
94
95 28 osmith
h3. Running it natively on your machine
96 2 laforge
97
This is the most complicated bit to set-up, as you will have to run the respective Osmocom Program (Implementation Under Test) in the right configuration with all the IP addresses, port numbers, config file, etc. exactly like it's expected by the test suite.
98 1 laforge
99 14 osmith
You will need a deeper understanding about how the test suite works, and what its requirement are. Oftentimes looking at how it's done in the Docker scripts is helpful.
100
101
h4. Preparation
102
103
<pre>
104
$ apt install eclipse-titan
105
$ git clone git://osmocom.org/osmo-ttcn3-hacks
106
$ cd osmo-ttc3-hacks/deps
107
$ make
108
</pre>
109
110
h4. Compile a testsuite
111
112
Let's compile the @mgw@ testsuite for example:
113
114
<pre>
115
$ cd mgw
116
$ ./gen_links.sh
117 26 msuraev
$ ./regen_makefile.sh
118 14 osmith
</pre>
119 1 laforge
120 23 osmith
The next command will transform the TTCN3 test data into C++ code. Do not use @-j@ here, that won't work (and it is pretty fast anyway).
121 14 osmith
<pre>
122
$ make compile
123
</pre>
124
125 27 msuraev
Note: if you observe errors during @make compile@, try running it from top-level as @make mgw@ which should trigger dependency update.
126
127 14 osmith
Finally compile the testsuite:
128
<pre>
129
$ make -j5
130
</pre>
131 27 msuraev
132 14 osmith
h4. Run a testsuite
133
134 18 osmith
Start the component that is about to get tested with the config that the testsuite expects. Again, with @mgw@ as example. If you don't have a suitable config file, use "the one from Jenkins":https://git.osmocom.org/docker-playground/tree/ttcn3-mgw-test/osmo-mgw.cfg and replace all IPs with @127.0.0.1@.
135 14 osmith
<pre>
136 21 osmith
$ osmo-mgw -c osmo-mgw.cfg
137 14 osmith
</pre>
138
139
Then run the testsuite:
140
<pre>
141
$ cd osmo-ttcn3-hacks/mgw
142
$ ../start-testsuite.sh ./MGCP_test MGCP_Test.cfg
143
</pre>
144
145
Afterwards you can merge and format the logs as follows:
146
<pre>
147
$ ttcn3_logmerge MGCP_test*.log > ./merged.log
148 1 laforge
$ ttcn3_logformat ./merged.log > ./result.log
149 30 msuraev
</pre>
150
or
151
<pre>
152 31 msuraev
$ ../log_merge.sh MGCP_test
153 14 osmith
</pre>
154 2 laforge
155
h4. Running only a sub-set of the test cases
156
157 17 osmith
Running whole testsuites may take a long time. If you only want to run one specific test, or a subset of tests, open up the @_*Test.cfg@ file in the folder of the testsuite and edit the @[EXECUTE]@ section. For example, in "@MGCP_Test.cfg@":https://git.osmocom.org/osmo-ttcn3-hacks/tree/mgw/MGCP_Test.cfg from the @mgw@ folder it looks like the following: 
158 16 osmith
159
<pre>
160 1 laforge
...
161 17 osmith
[EXECUTE]
162
MGCP_Test.control
163
#MGCP_Test.TC_selftest
164
#MGCP_Test.TC_crcx
165
#MGCP_Test.TC_crcx_noprefix
166
...
167
</pre>
168 1 laforge
169 17 osmith
The only line that is *not* commented out is @MGCP_Test.control@. This @*.control@ line will cause all tests to be executed. So comment this line out, and then activate one of the lines of which you would like to execute the tests (see the example below). Then execute the testsuite as usually, and it will skip all commented out tests.
170
171
<pre>
172
...
173
[EXECUTE]
174
#MGCP_Test.control
175
#MGCP_Test.TC_selftest
176
MGCP_Test.TC_crcx
177
MGCP_Test.TC_crcx_noprefix
178
...
179 16 osmith
</pre>
180 2 laforge
181 15 osmith
h2. Reading the logs
182
183
* @xfail@ means, that a test is known to fail, @FAIL@ are unexpected test failures
184
* search for @setverdict(@ to find the results of single tests. @-> fail@ should be the location where a test is failing.
185
186 2 laforge
h2. Further information
187
188 22 osmith
* April 2018 talk by Harald on "State of the Osmocom TTCN-3 Test Suites":https://media.ccc.de/v/UGHHW3
Add picture from clipboard (Maximum size: 48.8 MB)