Project

General

Profile

coordination #43139

Assess and improve automation coverage for yast2-network

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

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
80.00 h

Description

Initial plan:

  1. Check current existing related tests, assess their relevance and extendability
  2. 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

#1 Updated by vsvecova over 2 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.

#2 Updated by brhavel over 2 years ago

  • Due date set to 2018-12-14

#3 Updated by brhavel over 2 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

#4 Updated by vsvecova over 2 years ago

Currently working on extending yast2_lan.pm

#5 Updated by vsvecova over 2 years ago

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

#6 Updated by vsvecova over 2 years ago

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

#7 Updated by vsvecova over 2 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

#8 Updated by brhavel over 2 years ago

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

#9 Updated by vsvecova over 2 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

#10 Updated by brhavel about 2 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

#11 Updated by brhavel about 2 years ago

  • Priority changed from Normal to Urgent

#12 Updated by brhavel over 1 year ago

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

#13 Updated by brhavel over 1 year 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

#14 Updated by tjyrinki_suse over 1 year 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)

#15 Updated by tjyrinki_suse over 1 year ago

  • Priority changed from Urgent to High

Readjusting priorities of several tasks to present them more hierarchically.

#16 Updated by vpelcak over 1 year ago

  • Priority changed from High to Normal

#17 Updated by vpelcak over 1 year 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

#18 Updated by vpelcak about 1 year ago

  • Priority changed from Normal to Urgent

#19 Updated by tjyrinki_suse about 1 year ago

  • Priority changed from Urgent to High

Adjusting priority orders of some tickets.

#20 Updated by vpelcak about 1 year ago

  • Priority changed from High to Urgent

#21 Updated by tjyrinki_suse about 1 year ago

  • Priority changed from Urgent to High

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

#22 Updated by tjyrinki_suse 9 months 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

#23 Updated by tjyrinki_suse 8 months ago

  • Project changed from QAM to qe-yast
  • 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.

#24 Updated by tjyrinki_suse 8 months 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

#25 Updated by riafarov 8 months 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

#26 Updated by riafarov 5 months ago

  • Tracker changed from action to coordination

Also available in: Atom PDF