Project

General

Profile

Actions

Feature #2516

closed

automatic testing of osmo-mgw / jenkins integration

Added by dexter over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
09/18/2017
Due date:
% Done:

100%

Spec Reference:

Description

Currently we test osmo-mgw with unit tests. It might make sense to run some more realistic tests. The idea is to start osmo-mgw in a testrig that then makes test connections and sends test data. The testrig could be a python program or even a TTCN3 test.

Some ideas:
  • Send command (e.g. CRCX) and inspect resulting internal states via VTY also check response for plausibility
  • Send odd command sequences, check if the expected error codes are generated.
  • Send malformed messages or incomplete messages, check if the expected error codes are generated
  • Create a full connection, send RTP packets through, check if the RTP packets take the right path
  • Create a loopback connection, send RTP packets, check if the packets are reflected correctly

Checklist

  • execute mgw test automatically by jenkins (like ggsn or sysinfo tests)

Related issues

Related to OsmoMGW - Feature #2703: extend mgw tests to test more actual RTP flowsResolveddexter12/03/2017

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)