https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-04-27T02:12:44ZOpen Source Mobile CommunicationsOsmoGSMTester - Feature #2193: write osmo-gsm-tester test cases and extend tester APIhttps://projects.osmocom.org/issues/2193?journal_id=37262017-04-27T02:12:44Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> OsmoGSMTester - Feature #2193: write osmo-gsm-tester test cases and extend tester APIhttps://projects.osmocom.org/issues/2193?journal_id=38672017-05-14T11:16:42Zlaforge
<ul><li><strong>Assignee</strong> deleted (<del><i>118</i></del>)</li></ul> OsmoGSMTester - Feature #2193: write osmo-gsm-tester test cases and extend tester APIhttps://projects.osmocom.org/issues/2193?journal_id=39092017-05-15T12:58:54Zlaforge
<ul><li><strong>Assignee</strong> set to <i>55360</i></li></ul> OsmoGSMTester - Feature #2193: write osmo-gsm-tester test cases and extend tester APIhttps://projects.osmocom.org/issues/2193?journal_id=51882017-08-25T16:50:33Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>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.</p>
<p>I am preprending this text nowadays to easily see tasks which are about adding new tests: "osmo-gsm-tester: add test case:"</p> OsmoGSMTester - Feature #2193: write osmo-gsm-tester test cases and extend tester APIhttps://projects.osmocom.org/issues/2193?journal_id=51922017-08-27T14:34:30Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>pespin wrote:</p>
<blockquote>
<p>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.</p>
<p>I am preprending this text nowadays to easily see tasks which are about adding new tests: "osmo-gsm-tester: add test case:"</p>
</blockquote>
<p>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.</p> OsmoGSMTester - Feature #2193: write osmo-gsm-tester test cases and extend tester APIhttps://projects.osmocom.org/issues/2193?journal_id=51942017-08-27T14:36:46Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>It is possible to detach issues from a parent task: edit the issue and remove the issue number from the "Parent task" edit field.<br />When we mark this parent task resolved, we should detach the open subtasks in this way.</p> OsmoGSMTester - Feature #2193: write osmo-gsm-tester test cases and extend tester APIhttps://projects.osmocom.org/issues/2193?journal_id=57012017-10-11T02:50:08Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>