Project

General

Profile

Feature #1998

jenkins integration of m3ua-testtool

Added by laforge 20 days ago. Updated 20 days ago.

Status:
New
Priority:
Low
Assignee:
Start date:
04/10/2017
Due date:
% Done:

0%

Spec Reference:

Description

The ETSI Test specifications for M3UA are published as TS 102 381 (http://www.etsi.org/deliver/etsi_ts/102300_102399/102381/01.01.01_60/ts_102381v010101p.pdf) and implemented in m3ua-testtool (https://github.com/nplab/m3ua-testtool)

We currently pass most of the (relevant) tests of m3ua-testtool, and it would be useful to have some kind of jenkins integration, where each new build is tested against those "known working" test cases.

The problem is (like any network related test) is that we can hardly make assumptions about the network configuration of the build node. Hence, it would be best to do this in a network namespace and exclude that test from executing on Platforms != Linux.

m3ua-testtool requires some local configuration (in the home of the user!) as well as guile (it's written in Scheme). Also, in order to test the SGW we need to run osmo-stp, also with respective configuration.

I can put together a set of m3ua-testtool and osmo-stp.cfg that will execute the tests (in a netns), but I would appreciate if somebody else could then look into the jenkins integration and the "bypass != Linux" side of things.

History

#1 Updated by laforge 20 days ago

Also available in: Atom PDF