action #26806
closedfate#320573: [sle][functional][y][mandatory][fate:done][R] Add 'services' view to yast2 sw_single
0%
Description
Adding Tests for the New "Services" View in the YaST Package Manager¶
We have implemented a new "Services" view in the YaST package manager and we would like to ask for creating openQA tests for it.
See https://fate.suse.com/320573 for more details about the feature.
Notes¶
The feature will be released in a SLE15 maintenance update, that means for testing in SLE15-SP0 you need a registered system with all maintenance updates applied. In SP1 it will be available directly on the installation media.
The "Services" view is available only when there is at least one libzypp service available. Services are usually added from a registration server (SCC), in theory users can use their own or 3rd party services but that's probably a rare scenario.
If no service is available (e.g. unregistered SLES installed from the Packages DVD or in openSUSE Leap) then the menu will not contain the "Services" item at all.
There is a small difference when using SMT as the registration server instead of SCC. SMT uses a single service for all registered modules/extensions. Which means the feature will not provide much value for the users as in that case they cannot easily filter packages by module or extension. But we cannot do much about it from the YaST POV, that's the SMT design which we cannot change.
Please note that the displayed service names from SCC contain ugly underscores. This has been reported as bug https://bugzilla.suse.com/show_bug.cgi?id=1099851 and might be potentially fixed in the future. Which means the needles might need an update in the future.
Screenshots¶
- Qt screenshot:
- Ncurses Screenshot
For testing you need these package versions (in SLE15):
- libyui-ncurses-pkg8 => 2.48.5.1
- libyui-qt-pkg8 => 2.45.15.1
Updated by okurz over 6 years ago
- Subject changed from fate#320573: [sle][functional][mandatory][R] Add 'services' view to yast2 sw_single to fate#320573: [sle][functional][mandatory][fate:ready][R] Add 'services' view to yast2 sw_single
- Status changed from New to Blocked
- Target version changed from Milestone 13 to Milestone 14
backlink on fate, inserted mgriessmeier as QA tester, inserted myself as QA reviewer.
Feature is in state "ready". No movement on the fate issue since 2017-04, please review again in M14.
Updated by okurz about 6 years ago
- Due date set to 2018-04-24
- Target version changed from Milestone 14 to Milestone 15
no movement in fate
Updated by okurz about 6 years ago
- Due date deleted (
2018-04-24) - Target version changed from Milestone 15 to Milestone 17
fate was updated by PM to "After GA".
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 21+
was updated to "POST-GM". I guess this means for us to validate in SLE15SP1
Updated by okurz almost 6 years ago
- Subject changed from fate#320573: [sle][functional][mandatory][fate:ready][R] Add 'services' view to yast2 sw_single to fate#320573: [sle][functional][y][mandatory][fate:ready][R] Add 'services' view to yast2 sw_single
- Assignee deleted (
mgriessmeier)
adding [y], removing [u]-mgriessmeier :)
Updated by okurz almost 6 years ago
- Subject changed from fate#320573: [sle][functional][y][mandatory][fate:ready][R] Add 'services' view to yast2 sw_single to fate#320573: [sle][functional][y][mandatory][fate:done][R] Add 'services' view to yast2 sw_single
- Description updated (diff)
- Status changed from Blocked to Workable
Incorporating content from #38585
Updated by okurz almost 6 years ago
- Has duplicate action #38585: [functional][y] Create new openQA tests for the new "Services" view in the YaST package manager (FATE#320573) added
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21+ to Milestone 18
feature is ready now and assumed to be in the products openSUSE Tumbleweed and SLE15+updates. So we can test once exploratory, then evaluate a very simple automated test as next step and then steps to extend and improve on that.
Updated by okurz over 5 years ago
- Due date set to 2018-10-09
- Target version changed from Milestone 18 to Milestone 19
Updated by JERiveraMoya over 5 years ago
- Status changed from Workable to In Progress
Starting manual testing covering two scenarios:
- When registered system: for instance I will use, .qcow from https://openqa.suse.de/tests/2105203#step/scc_registration/14
- When unregistered system: I cannot find .qcow with unregistered system, ... strange, should we have one?
Updated by JERiveraMoya over 5 years ago
On a registered system in text mode Service is available in Filter but in gui is not available under View. Bug - Service tab is not visible under View in gui mode but it is visible in text mode
On an unregistered system I tested only in textmode (I don't know how to end up with a full gnome installation from scratch) using SUSEConnect to register the system, installing some related yast2 via zypper and checking that the modules are displayed in Service, also installing a new module (besides the ones by default when registering) in this case Desktop module to match with the registered system and checking that is also displayed.
Updated by JERiveraMoya over 5 years ago
- Status changed from In Progress to Blocked
Updated by okurz over 5 years ago
JERiveraMoya wrote:
On an unregistered system I tested only in textmode (I don't know how to end up with a full gnome installation from scratch)
I guess the easiest way is to follow the steps which you can also follow in the according gnome openQA scenario, that is: Register the system during installation, select (at least) the "Desktop Applications Module" and continue installation and you should end up in gnome.
Updated by JERiveraMoya over 5 years ago
That is the first scenario, a registered system on installation time. That is covered. The second is about a non-registered system in installation time and to use SUSEConnect afterward for registering and adding the modules, that is covered in text mode, because there are many package and (for me an unknown set of steps if it is even possible) needed to convert that text mode/minimal rol (result of an installation without registration like in this case https://openqa.suse.de/tests/2096007#step/system_role/3) to a gnome and check YaST in gui mode.
Updated by okurz over 5 years ago
JERiveraMoya wrote:
[…] use SUSEConnect afterward for registering and adding the modules, that is covered in text mode, because there are many package and (for me an unknown set of steps if it is even possible) needed to convert that text mode/minimal rol (result of an installation without registration like in this case https://openqa.suse.de/tests/2096007#step/system_role/3) to a gnome […]
Yes, it is possible by registering the system and activating the "desktop applications" module with SUSEConnect and then install the gnome(?) pattern, e.g. zypper in -t pattern gnome … or similar. But I would not invest any additional effort into this approach.
Updated by JERiveraMoya over 5 years ago
- Status changed from Blocked to Resolved
That makes sense with that pattern but you're right no needed here.
I commented about the bug in fate and resolving this ticket according to our process.