coordination #43139: Assess and improve automation coverage for yast2-network - qe-yam - openSUSE Project Management Tool

Custom queries

openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
QE Yam backlog
QE Yam blocked issues
QE Yam closed yesterday
QE Yam issues IN_PROGRESS
QE Yam new action tickets per day
QE Yam new actions
QE Yam prio high, no updates last 4 weeks
QE Yam prio low & normal, no update for 1 year
QE Yam recjected yesterday
QE Yam resolved yesterday
QE Yam workable actions
soft failure tickets in progress
softfailure tickets resolved
softfailure tickets workable
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

coordination #43139

closed

Assess and improve automation coverage for yast2-network

Added by vsvecova over 5 years ago. Updated almost 2 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Target version:

QA - future

Start date:

Due date:

% Done:

Estimated time:

80.00 h

Description

Initial plan:

Check current existing related tests, assess their relevance and extendability
Adapt test scenarios from https://bugzilla.suse.com/tr_list_cases.cgi?tags_type=anyexact&tags=packagename_yast2-network and from regression testing sections of past test reports.

History
Notes
Property changes

Actions

Copy link

Updated by vsvecova over 5 years ago

Status changed from New to In Progress
Target version set to QAM tests - current

Current progress: working on developing a suitable test scenario in line with initial plans.

Actions

Copy link

Updated by brhavel over 5 years ago

Due date set to 2018-12-14

Actions

Copy link

Updated by brhavel over 5 years ago

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

Actions

Copy link

Updated by vsvecova over 5 years ago

Currently working on extending yast2_lan.pm

Actions

Copy link

Updated by vsvecova over 5 years ago

Current plan is to run the progress by Petr/Martin by this Friday and then proceed in line with their feedback/suggestions.

Actions

Copy link

Updated by vsvecova over 5 years ago

Finishing touches, adding missing needles etc. Then gather feedback.

Actions

Copy link

Updated by vsvecova over 5 years ago

As verification runs have revealed, the test code requires additional adjustments due to differences introduced into yast2-network in SLE15-SP1.

See relevant yast team trello card for details on the changes: https://trello.com/c/so0amSNp/342-sle-15-sp1-yast2-network-clarify-hostname-setup

Actions

Copy link

Updated by brhavel over 5 years ago

Due date changed from 2018-12-14 to 2019-02-01

Actions

Copy link

Updated by vsvecova about 5 years ago

Subject changed from [qam] Assess and improve automation coverage for yast2-network to [qam] [yellow] Assess and improve automation coverage for yast2-network

Actions

Copy link

#10

Updated by brhavel about 5 years ago

Subject changed from [qam] [yellow] Assess and improve automation coverage for yast2-network to [qam][yellow][urgent] Assess and improve automation coverage for yast2-network

Actions

Copy link

#11

Updated by brhavel almost 5 years ago

Priority changed from Normal to Urgent

Actions

Copy link

#12

Updated by brhavel over 4 years ago

as the test was already finished and is running, can we resolve the ticket and address maintenance in separated tickets?

Actions

Copy link

#13

Updated by brhavel over 4 years ago

Subject changed from [qam][yellow][urgent] Assess and improve automation coverage for yast2-network to [qam][maint][yast2-network][urgent] Assess and improve automation coverage for yast2-network

Actions

Copy link

#14

Updated by tjyrinki_suse about 4 years ago

Status changed from In Progress to Blocked
Assignee deleted (~~vsvecova~~)

Unassigning since no progress and not part of current sprint, assuming blocked. (please update with any information)

Actions

Copy link

#15

Updated by tjyrinki_suse about 4 years ago

Priority changed from Urgent to High

Readjusting priorities of several tasks to present them more hierarchically.

Actions

Copy link

#16

Updated by vpelcak about 4 years ago

Priority changed from High to Normal

Actions

Copy link

#17

Updated by vpelcak about 4 years ago

Subject changed from [qam][maint][yast2-network][urgent] Assess and improve automation coverage for yast2-network to [qam][maint][yast2-network] Assess and improve automation coverage for yast2-network

Actions

Copy link

#18

Updated by vpelcak about 4 years ago

Priority changed from Normal to Urgent

Actions

Copy link

#19

Updated by tjyrinki_suse almost 4 years ago

Priority changed from Urgent to High

Adjusting priority orders of some tickets.

Actions

Copy link

#20

Updated by vpelcak almost 4 years ago

Priority changed from High to Urgent

Actions

Copy link

#21

Updated by tjyrinki_suse almost 4 years ago

Priority changed from Urgent to High

At most High priority for new package specific tests that have score <10. yast2-network is 8.

Actions

Copy link

#22

Updated by tjyrinki_suse over 3 years ago

Subject changed from [qam][maint][yast2-network] Assess and improve automation coverage for yast2-network to [qe-core][qam][maint][yast2-network] Assess and improve automation coverage for yast2-network

Actions

Copy link

#23

Updated by tjyrinki_suse over 3 years ago

Project changed from 119 to qe-yam
Due date deleted (~~2019-02-01~~)
Status changed from Blocked to New
Priority changed from High to Normal
Target version deleted (~~QAM tests - current~~)
Start date deleted (~~2018-10-30~~)

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.

Actions

Copy link

#24

Updated by tjyrinki_suse over 3 years ago

Subject changed from [qe-core][qam][maint][yast2-network] Assess and improve automation coverage for yast2-network to [qem][maint][yast2-network] Assess and improve automation coverage for yast2-network

Actions

Copy link

#25

Updated by riafarov over 3 years ago

Subject changed from [qem][maint][yast2-network] Assess and improve automation coverage for yast2-network to Assess and improve automation coverage for yast2-network
Target version set to future

Actions

Copy link

#26

Updated by riafarov about 3 years ago

Tracker changed from action to coordination

Actions

Copy link

#27

Updated by JERiveraMoya almost 2 years ago

Status changed from New to Rejected

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.

Actions

Copy link

Also available in: Atom PDF

Project

General

Profile

QA » openQA Project » openQA Tests » qe-yam

Tags

Custom queries

coordination #43139

Assess and improve automation coverage for yast2-network

Updated by vsvecova over 5 years ago

Updated by brhavel over 5 years ago

Updated by brhavel over 5 years ago

Updated by vsvecova over 5 years ago

Updated by vsvecova over 5 years ago

Updated by vsvecova over 5 years ago

Updated by vsvecova over 5 years ago

Updated by brhavel over 5 years ago

Updated by vsvecova about 5 years ago

Updated by brhavel about 5 years ago

Updated by brhavel almost 5 years ago

Updated by brhavel over 4 years ago

Updated by brhavel over 4 years ago

Updated by tjyrinki_suse about 4 years ago

Updated by tjyrinki_suse about 4 years ago

Updated by vpelcak about 4 years ago

Updated by vpelcak about 4 years ago

Updated by vpelcak about 4 years ago

Updated by tjyrinki_suse almost 4 years ago

Updated by vpelcak almost 4 years ago

Updated by tjyrinki_suse almost 4 years ago

Updated by tjyrinki_suse over 3 years ago

Updated by tjyrinki_suse over 3 years ago

Updated by tjyrinki_suse over 3 years ago

Updated by riafarov over 3 years ago

Updated by riafarov about 3 years ago

Updated by JERiveraMoya almost 2 years ago