https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-11-07T17:56:58ZopenSUSE Project Management Toolqe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1634752018-11-07T17:56:58Zvsvecovaveronika.svecova@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Target version</strong> set to <i>QAM tests - current</i></li></ul><p>Current progress: working on developing a suitable test scenario in line with initial plans.</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1645702018-11-13T15:14:29Zbrhavelbhavel@suse.com
<ul><li><strong>Due date</strong> set to <i>2018-12-14</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1684432018-11-26T09:17:47Zbrhavelbhavel@suse.com
<ul></ul><p>As far as I know, Veronika prepared the coverage to implement for this particular test (test plan) which is going to be implemented once she is back from vacation</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1750702018-12-19T10:10:31Zvsvecovaveronika.svecova@suse.com
<ul></ul><p>Currently working on extending yast2_lan.pm</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1762792019-01-03T12:16:15Zvsvecovaveronika.svecova@suse.com
<ul></ul><p>Current plan is to run the progress by Petr/Martin by this Friday and then proceed in line with their feedback/suggestions.</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1793992019-01-15T11:41:12Zvsvecovaveronika.svecova@suse.com
<ul></ul><p>Finishing touches, adding missing needles etc. Then gather feedback.</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1820902019-01-24T17:42:46Zvsvecovaveronika.svecova@suse.com
<ul></ul><p>As verification runs have revealed, the test code requires additional adjustments due to differences introduced into yast2-network in SLE15-SP1.</p>
<p>See relevant yast team trello card for details on the changes: <a href="https://trello.com/c/so0amSNp/342-sle-15-sp1-yast2-network-clarify-hostname-setup" class="external">https://trello.com/c/so0amSNp/342-sle-15-sp1-yast2-network-clarify-hostname-setup</a></p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=1836112019-01-30T15:54:08Zbrhavelbhavel@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-12-14</i> to <i>2019-02-01</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2007772019-03-20T11:09:37Zvsvecovaveronika.svecova@suse.com
<ul><li><strong>Subject</strong> changed from <i>[qam] Assess and improve automation coverage for yast2-network </i> to <i>[qam] [yellow] Assess and improve automation coverage for yast2-network </i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2100682019-05-06T10:27:16Zbrhavelbhavel@suse.com
<ul><li><strong>Subject</strong> changed from <i>[qam] [yellow] Assess and improve automation coverage for yast2-network </i> to <i>[qam][yellow][urgent] Assess and improve automation coverage for yast2-network </i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2236432019-07-02T06:44:56Zbrhavelbhavel@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2598892019-11-26T14:11:36Zbrhavelbhavel@suse.com
<ul></ul><p>as the test was already finished and is running, can we resolve the ticket and address maintenance in separated tickets?</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2619652019-12-05T08:11:41Zbrhavelbhavel@suse.com
<ul><li><strong>Subject</strong> changed from <i>[qam][yellow][urgent] Assess and improve automation coverage for yast2-network </i> to <i>[qam][maint][yast2-network][urgent] Assess and improve automation coverage for yast2-network </i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2802912020-02-25T08:56:07Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Blocked</i></li><li><strong>Assignee</strong> deleted (<del><i>vsvecova</i></del>)</li></ul><p>Unassigning since no progress and not part of current sprint, assuming blocked. (please update with any information)</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2816532020-02-28T09:25:17Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>High</i></li></ul><p>Readjusting priorities of several tasks to present them more hierarchically.</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2829792020-03-04T10:58:24Zvpelcakvpelcak@suse.com
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2948752020-04-21T19:47:16Zvpelcakvpelcak@suse.com
<ul><li><strong>Subject</strong> changed from <i>[qam][maint][yast2-network][urgent] Assess and improve automation coverage for yast2-network </i> to <i>[qam][maint][yast2-network] Assess and improve automation coverage for yast2-network </i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=2980152020-05-05T12:05:19Zvpelcakvpelcak@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3037152020-05-29T08:10:43Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>High</i></li></ul><p>Adjusting priority orders of some tickets.</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3048072020-06-03T09:10:14Zvpelcakvpelcak@suse.com
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3052032020-06-04T12:57:17Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>High</i></li></ul><p>At most High priority for new package specific tests that have score <10. yast2-network is 8.</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3474642020-11-06T07:25:27Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Subject</strong> changed from <i>[qam][maint][yast2-network] Assess and improve automation coverage for yast2-network </i> to <i>[qe-core][qam][maint][yast2-network] Assess and improve automation coverage for yast2-network </i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3546442020-11-26T12:47:59Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Project</strong> changed from <i>119</i> to <i>qe-yam</i></li><li><strong>Due date</strong> deleted (<del><i>2019-02-01</i></del>)</li><li><strong>Status</strong> changed from <i>Blocked</i> to <i>New</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li><li><strong>Target version</strong> deleted (<del><i>QAM tests - current</i></del>)</li><li><strong>Start date</strong> deleted (<del><i>2018-10-30</i></del>)</li></ul><p>One more QE Yast issue found that likely is not more relevant than any other old/stale ones and could be, once time for cleaning up all the old tickets, evaluated together with the whole current setup.</p>
qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3546462020-11-26T12:48:08Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Subject</strong> changed from <i>[qe-core][qam][maint][yast2-network] Assess and improve automation coverage for yast2-network </i> to <i>[qem][maint][yast2-network] Assess and improve automation coverage for yast2-network </i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3550182020-11-27T07:56:04Zriafarov
<ul><li><strong>Subject</strong> changed from <i>[qem][maint][yast2-network] Assess and improve automation coverage for yast2-network </i> to <i>Assess and improve automation coverage for yast2-network </i></li><li><strong>Target version</strong> set to <i>future</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=3826452021-02-15T12:12:32Zriafarov
<ul><li><strong>Tracker</strong> changed from <i>action</i> to <i>coordination</i></li></ul> qe-yam - coordination #43139: Assess and improve automation coverage for yast2-network https://progress.opensuse.org/issues/43139?journal_id=5368032022-07-14T12:37:10ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>For now we still don't plan to extend test coverage, and even less in the area of networking as libyui REST afik would not work out of the box.</p>