action #33070
closed[bsc#1082535] add test to verify YaST dev packages in Dev Tools module
0%
Description
Motivated by https://bugzilla.suse.com/show_bug.cgi?id=1082535
After discussion with Ladislav, we would like to at least check if packages are available in the module and can be installed.
To verify some real scenario, we should also run following commands:
In installed system:
- Run "git clone" to download some YaST package sources
- Run "rake test:unit" to run the unit tests
- Run "rake install" to install the package from sources
This will ensure that no dependencies are missing.
Acceptance criteria¶
- AC1: Test verifies that packages and dependencies are available in Dev Tools module and are installable
- AC2: Test verifies that rake commands work for some YaST module project
Updated by okurz about 6 years ago
- Description updated (diff)
- Target version set to Milestone 17
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][yast][regression][bsc#1082535] add test to verify YaST dev packages in Dev Tools module to [sle][functional][y][yast][regression][bsc#1082535] add test to verify YaST dev packages in Dev Tools module
- Target version changed from Milestone 17 to Milestone 19
I guess M17 is a bit too early.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 19 to Milestone 19
Updated by okurz over 5 years ago
- Target version changed from Milestone 19 to future
I have the feeling that having an openQA test to ensure this is not the right approach. Probably some more "static" checks on the medium should be considered. Maybe based on the containers of the products? :)
Updated by riafarov over 3 years ago
- Project changed from openQA Tests to qe-yam
- Subject changed from [sle][functional][y][yast][regression][bsc#1082535] add test to verify YaST dev packages in Dev Tools module to [bsc#1082535] add test to verify YaST dev packages in Dev Tools module
- Category deleted (
New test)
Updated by okurz over 2 years ago
- Priority changed from Normal to Low
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)