Project

General

Profile

Feature #2193

write osmo-gsm-tester test cases and extend tester API

Added by neels 10 months ago. Updated 4 months ago.

Status:
Closed
Priority:
High
Assignee:
osmo-gsm-tester
Target version:
-
Start date:
04/26/2017
Due date:
% Done:

50%

Spec Reference:

Description

So far we have only a simplistic send+receive SMS test case.
This is a parent issue for the various test cases we would like to be added in a short timeframe.


Subtasks

Feature #2198: osmo-gsm-tester: add test case using SMPP to send/receive SMSClosedpespin

Feature #2199: osmo-gsm-tester: provide API to reflect whether an osmo-nitb has started successfullyRejectedosmo-gsm-tester

Feature #2203: osmo-gsm-tester: add test case: data test APINewosmo-gsm-tester

Feature #2204: osmo-gsm-tester: add test case: CS paging while GPRS is activeNewosmo-gsm-tester

Feature #2213: osmo-gsm-tester: implement ofono integration to receive SMSClosedneels

Feature #2309: osmo-gsm-tester: add test case: smpp: transaction modeClosedosmo-gsm-tester

Feature #2310: osmo-gsm-tester: add test case: smpp: normal mode (store&forward)Closedpespin

Feature #2311: osmo-gsm-tester: add test case: smpp: smpp_first featureNewosmo-gsm-tester

Feature #2312: osmo-gsm-tester: add test case: smpp: passwordClosedosmo-gsm-tester

Feature #2313: osmo-gsm-tester: add test case: smpp: imsi extensionNewosmo-gsm-tester

Feature #2314: osmo-gsm-tester: add test case: smpp: correct ESME routingNewosmo-gsm-tester

Feature #2374: osmo-gsm-tester: add test case: sms between MS with delivery reportNewosmo-gsm-tester

History

#1 Updated by neels 10 months ago

  • Priority changed from Normal to High

#2 Updated by laforge 9 months ago

  • Assignee deleted (Osmocom Developers)

#3 Updated by laforge 9 months ago

  • Assignee set to osmo-gsm-tester

#4 Updated by pespin 6 months ago

  • Status changed from New to Resolved

This task is too generic and it's going to be a never-ending task, because it just packs subtasks. I think we can close it.

I am preprending this text nowadays to easily see tasks which are about adding new tests: "osmo-gsm-tester: add test case:"

#5 Updated by neels 6 months ago

pespin wrote:

This task is too generic and it's going to be a never-ending task, because it just packs subtasks. I think we can close it.

I am preprending this text nowadays to easily see tasks which are about adding new tests: "osmo-gsm-tester: add test case:"

Agreed. It seemed logical to have a parent / subtask structure, but since then I have had headaches with this kind of structuring. It is less trouble to keep single issues without parent task structure. We could use tags (probably needs a plugin installed, we have it on the sysmocom internal redmine) -- but I am so far not disciplined at keeping tags accurate.

#6 Updated by neels 6 months ago

It is possible to detach issues from a parent task: edit the issue and remove the issue number from the "Parent task" edit field.
When we mark this parent task resolved, we should detach the open subtasks in this way.

#7 Updated by laforge 4 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF