action #26984

[sle][functional][y] New test scenario: minimal+proxy_SCC-postreg_yast_scc

Added by Anonymous over 2 years ago. Updated about 1 year ago.

Status:RejectedStart date:24/10/2017
Priority:NormalDue date:
Assignee:riafarov% Done:

0%

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

Description

Acceptance criteria

  • AC1: Have a test scenario for SLE12 to test registration and modules addition using yast_scc against proxy-SCC on ncurses and x11.
  • AC2: Have a test scenario for SLE15 to test modules addition using yast_scc against proxy-SCC on ncurses and x11.

Tasks

  1. Adapt SLE12 ncurses tests to register and add modules using yast2_scc using two modules.
  2. Reuse modules from SLE12 for SLE15, skipping registration module for yast2_scc, since SLE15 is already registered when using yast2_scc.
  3. Create a new test suite textmode+proxy_SCC-yast2scc_ for SLE15

Further details


Related issues

Related to openQA Tests - action #19566: [sle][functional]New test scenario: minimal+proxy_SCC-pos... Resolved 04/06/2017 08/11/2017
Duplicated by openQA Tests - action #27028: [sle][functional]test fails in addon_products_via_SCC_yas... Resolved 25/10/2017
Blocked by openQA Tests - action #27064: [functional][x86_64][s390x][uefi][y][yast][easy] Test sui... Resolved 27/10/2017 27/03/2018

History

#1 Updated by okurz over 2 years ago

  • Related to action #19566: [sle][functional]New test scenario: minimal+proxy_SCC-postreg_suseconnect_scc added

#2 Updated by okurz over 2 years ago

so let's not schedule that one for the next sprint, not yet workable

#4 Updated by okurz over 2 years ago

  • Due date set to 08/11/2017
  • Status changed from New to In Progress

you stated "should be already done" so with this confidence let's add it.

#5 Updated by okurz over 2 years ago

  • Related to action #27028: [sle][functional]test fails in addon_products_via_SCC_yast2 - test does not expect that the system is already registered added

#6 Updated by okurz over 2 years ago

  • Category set to New test

the test module "addon_products_via_SCC_yast2" looks very similar, please take a look in #27028 and crosscheck

#7 Updated by SLindoMansilla over 2 years ago

  • Subject changed from [sle][functional]New test scenario: minimal+proxy_SCC-postreg_yast_scc to [sle][functional] New test scenario: minimal+proxy_SCC-postreg_yast_scc
  • Description updated (diff)

Changes on acceptance criteria and tasks because of poo#27028
Actually the scope of this ticket is also affected by legacy tests from SLE12.

#8 Updated by SLindoMansilla over 2 years ago

  • Related to deleted (action #27028: [sle][functional]test fails in addon_products_via_SCC_yast2 - test does not expect that the system is already registered)

#9 Updated by SLindoMansilla over 2 years ago

  • Duplicated by action #27028: [sle][functional]test fails in addon_products_via_SCC_yast2 - test does not expect that the system is already registered added

#10 Updated by SLindoMansilla over 2 years ago

  • Description updated (diff)

#11 Updated by SLindoMansilla over 2 years ago

  • Description updated (diff)

#12 Updated by SLindoMansilla over 2 years ago

  • Blocked by action #27064: [functional][x86_64][s390x][uefi][y][yast][easy] Test suite minimal+base+sdk+proxy_SCC-postreg had a wrong scheduled module list with current version of os-autoinst-distri-opensuse added

#13 Updated by SLindoMansilla over 2 years ago

  • Description updated (diff)

#14 Updated by okurz over 2 years ago

  • Due date deleted (08/11/2017)

not done, needs re-evaluation

#15 Updated by okurz over 2 years ago

  • Target version set to Milestone 12

#16 Updated by SLindoMansilla over 2 years ago

  • Assignee deleted (SLindoMansilla)

Unassigned because it is not in this sprint nor in the next one, to clean my "assigned ticket" list.

#17 Updated by riafarov about 2 years ago

  • Status changed from In Progress to Workable

#18 Updated by okurz about 2 years ago

  • Blocked by action #30706: [sle][functional[sle12 sp4] test fails in boot_to_desktop - needle 'grub2' not found added

#19 Updated by okurz about 2 years ago

  • Blocked by deleted (action #30706: [sle][functional[sle12 sp4] test fails in boot_to_desktop - needle 'grub2' not found )

#20 Updated by okurz about 2 years ago

  • Description updated (diff)
  • Due date set to 10/04/2018
  • Status changed from Workable to Blocked
  • Target version changed from Milestone 12 to Milestone 15

see blocking ticket

#21 Updated by okurz about 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: sles+sdk+proxy_SCC_via_YaST
https://openqa.suse.de/tests/1461431

#22 Updated by okurz about 2 years ago

  • Assignee set to okurz
  • Target version changed from Milestone 15 to Milestone 17

blocked by ticket in M17

#23 Updated by okurz about 2 years ago

  • Subject changed from [sle][functional] New test scenario: minimal+proxy_SCC-postreg_yast_scc to [sle][functional][y] New test scenario: minimal+proxy_SCC-postreg_yast_scc
  • Description updated (diff)
  • Due date changed from 10/04/2018 to 22/05/2018
  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)
  • Target version changed from Milestone 17 to Milestone 16

#24 Updated by okurz almost 2 years ago

  • Due date deleted (22/05/2018)
  • Target version changed from Milestone 16 to Milestone 19

Does not have an effect on SLE15 anymore, we can postpone this in favor of other tasks now

#25 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 19 to Milestone 19

#26 Updated by riafarov over 1 year ago

  • Due date set to 06/11/2018

#27 Updated by okurz over 1 year ago

  • Due date deleted (06/11/2018)
  • Target version changed from Milestone 19 to future

#28 Updated by riafarov about 1 year ago

  • Status changed from Workable to Rejected
  • Assignee set to riafarov

By now we have scenarios covering AC, except that it's not running for ncurses and x11, whereas, knowing how libyui is designed, risks are low that something will break in qt and not in ncurses or vice versa. And if there is such an issue we will notice it for installations handled in qt vs ncurses + other test scenarios where we run tests against both versions (e.g. yast2_lan and yast2_i, which are executed for X11 and ncurses)

Also available in: Atom PDF