Titan TTCN3 Testsuites » History » Revision 3
« Previous |
Revision 3/52
(diff)
| Next »
osmith, 09/03/2018 12:45 PM
fix typo
- Table of contents
- Osmocom Titan TTCN3 Testsuites
Osmocom Titan TTCN3 Testsuites¶
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 + executor of the Eclipse_TITAN project.
Source Code / Patches¶
The source code of our test suites lives in theosmo-ttcn3-hacks
repository
- cgit web interface: http://git.osmocom.org/osmo-ttcn3-hacks/
- clone:
git clone git://git.osmocom.org/osmo-ttcn3-hacks
- patch review: https://gerrit.osmocom.org/#/q/project:osmo-ttcn3-hacks
We're following the Gerrit process for patch review.
Test Suites¶
Running a testsuite¶
You have multiple options on how to execute a test suite.
Running test suite in the dockerized environment¶
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" addrsses between IUT and testsuite.
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.
The docker files for this can be found in the docker-playground
git repository which you can clone from git://git.osmocom.org/docker-playground
- look at http://git.osmocom.org/docker-playground/tree/ttcn3-bsc-test/jenkins.sh to understand which containers are required.
- at the time of writing, this is
osmo-stp-master
,osmo-bsc-master
,osmo-bts-master
andttcn3-bsc-test
- at the time of writing, this is
- build those respective containers by issuing
make
in the above-mentioned directories, e.g.$ (cd osmo-stp-master && make) $ (cd osmo-bsc-master && make) $ (cd osmo-bts-master && make) $ (cd ttcn3-bsc-test && make)
- run the
jenkins.sh
script of thettcn3-bsc-test
suite:$ cd ttcn3-bts-test && ./jenkins.sh
jenkins.sh
script will make sure to
- create the needed docker network[s]
- run all the required containers (IUT, helpers, testsuite)
- shut them down after test suite execution
- collect the log files after execution,
/tmp/logs
will contain them
Running only a sub-set of the test cases¶
FIXME
Running it native on your machine¶
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.
You will need a deeper understanding about how the test suite works, and what its requirement are.
Running only a sub-set of the test cases¶
FIXME
Further information¶
- April 2018 talk by Harald on State of he Osmocom TTCN-3 Test Suites
Updated by osmith over 5 years ago · 3 revisions