Project

General

Profile

Actions

Feature #2193

closed

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

Added by neels almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
-
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 11 (4 open7 closed)

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

Actions
Feature #2199: osmo-gsm-tester: provide API to reflect whether an osmo-nitb has started successfullyRejected04/26/2017

Actions
Feature #2203: osmo-gsm-tester: add test case: data test APIResolved04/26/2017

Actions
Feature #2213: osmo-gsm-tester: implement ofono integration to receive SMSClosedneels04/27/2017

Actions
Feature #2309: osmo-gsm-tester: add test case: smpp: transaction modeClosed05/31/2017

Actions
Feature #2310: osmo-gsm-tester: add test case: smpp: normal mode (store&forward)Closedpespin05/31/2017

Actions
Feature #2311: osmo-gsm-tester: add test case: smpp: smpp_first featureNew05/31/2017

Actions
Feature #2312: osmo-gsm-tester: add test case: smpp: passwordClosed05/31/2017

Actions
Feature #2313: osmo-gsm-tester: add test case: smpp: imsi extensionNew05/31/2017

Actions
Feature #2314: osmo-gsm-tester: add test case: smpp: correct ESME routingNew05/31/2017

Actions
Feature #2374: osmo-gsm-tester: add test case: sms between MS with delivery reportNew07/18/2017

Actions
Actions #1

Updated by neels almost 7 years ago

  • Priority changed from Normal to High
Actions #2

Updated by laforge almost 7 years ago

  • Assignee deleted (118)
Actions #3

Updated by laforge almost 7 years ago

  • Assignee set to 55360
Actions #4

Updated by pespin over 6 years 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:"

Actions #5

Updated by neels over 6 years 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.

Actions #6

Updated by neels over 6 years 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.

Actions #7

Updated by laforge over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)