Project

General

Profile

action #11708

Add-on installation: review zypper_lr testcase

Added by maritawerner about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
michalnowak
Category:
-
Start date:
2016-04-25
Due date:
% Done:

0%

Estimated time:
Difficulty:
Duration:

Description

After the installation the pool channels should be added and tested but it seems that the testcase zypper_lr does not do that properly, no needles are visible,
e.g. https://openqa.suse.de/tests/356456/modules/zypper_lr/steps/1


Related issues

Related to openQA Tests - action #11460: Feature 320494: Disable installation source after installation if we register systemResolved2016-04-01

History

#1 Updated by okurz about 4 years ago

  • Target version changed from 168 to Milestone 3

#2 Updated by michalnowak about 4 years ago

  • Status changed from New to In Progress

So, I guess the task is to make sure that zypper_lr verifies that zypper lr produces something sensible apart from verifying the command exits with return code 0.

#3 Updated by okurz about 4 years ago

I think the idea Marita had referencing the specific example is that the "zypper_lr" test case does not check that the sdk ftp repo is actually present. I fear needling the expected output will be quite error prone and tedious to support all different cases we have. I am thinking of wait_serial checking for what you expect, which might be tricky as we would need to know the repo paths for the corresponding addon. Can you investigate how the output of zypper_lr should look like per addon?

Also attending https://progress.opensuse.org/projects/openqatests/wiki#Definition-of-READY-for-new-tests might help as a checklist to get it covered. Ask marita for details if you are unsure.

#4 Updated by maritawerner about 4 years ago

Here

https://wiki.microfocus.net/index.php/SLE12_SP2_Channels_Checking_Table

you can find a Table of all Channels. But I think that update channels are only visible with real SCC and not with proxy SCC. I have to double check that next week.

#5 Updated by michalnowak about 4 years ago

  • Assignee set to michalnowak

#6 Updated by michalnowak about 4 years ago

Did not get you messages as I failed to assign this PR to me. But I believe I came up with a similar approach: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1495. To test all those addons combinations I extended addons_product_sle.pm: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1496. Plus quite a few needles: https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/160/.

#7 Updated by dgutu almost 4 years ago

  • Related to action #11460: Feature 320494: Disable installation source after installation if we register system added

#8 Updated by michalnowak almost 4 years ago

Looking at Acceptance test groups at openqa.s.de the test is being executed and is not failing anywhere, I believe this PR should be closed as resolved.

#9 Updated by okurz almost 4 years ago

  • Status changed from In Progress to Resolved

yes, I agree. Feel free to set the status to RESOLVED yourself next time, especially if you backed your decision by hard facts, i.e. as you stated, no failures in recent builds :-)

Also available in: Atom PDF