action #28555

[sle][functional][yast][y] create installation workflow which covers steps backward and changing system role

Added by zluo about 2 years ago. Updated 12 months ago.

Status:NewStart date:29/11/2017
Priority:LowDue date:
Assignee:-% Done:

0%

Category:New test
Target version:QA - future
Difficulty:
Duration:

Description

We got problem with installation workflow if it goes back and changes something for installation like changing system roles or packages.
Please see following bug report for example:

https://bugzilla.suse.com/show_bug.cgi?id=1069716

History

#1 Updated by okurz about 2 years ago

  • Category changed from Enhancement to existing tests to New test

Yes, good idea. This is actually "new test" as the test case is "go back and forth". Not any test we have. Of course, it would be interlinked with existing openQA test code.

#2 Updated by okurz about 2 years ago

  • Subject changed from [sles][functional] create installation workflow which covers steps backward and changing system role to [sle][functional] create installation workflow which covers steps backward and changing system role
  • Target version set to Milestone 15

#3 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 15 to Milestone 17

Seems like neither in M15 nor in M16 we do have enough capacity for new tests so we need to postpone to later.

#4 Updated by okurz almost 2 years ago

  • Subject changed from [sle][functional] create installation workflow which covers steps backward and changing system role to [sle][functional][yast][y] create installation workflow which covers steps backward and changing system role

#5 Updated by okurz over 1 year ago

  • Target version changed from Milestone 17 to Milestone 21+

#6 Updated by okurz over 1 year ago

  • Target version changed from Milestone 21+ to Milestone 21+

#7 Updated by okurz about 1 year ago

  • Target version changed from Milestone 21+ to Milestone 25

#8 Updated by okurz 12 months ago

  • Priority changed from Normal to Low
  • Target version changed from Milestone 25 to future

let's be honest, we should focus more on enhancing our current workflows rather than extending, decreasing prio, putting to "future"

Also available in: Atom PDF