[functional][y][epic] Reduce number of test suites used for YaST job group
We want to reduce number of the test suites and tools team has implemented scripts to detect such scenarios.
https://gitlab.suse.de/qsf-y/qa-sle-functional-y/merge_requests/131 can be used as a base, as some scenarios are already identified.
Idea is to use Test Suites and define there variable for the environment and other things in yaml schedule or in the test data structure.
#4 Updated by ybonatakis about 1 year ago
So the whole idea here is you can now define settings for jobs directly in the YAML, without using a testsuite.
this would reduce the number of testsuites we have in the database.
The candidates testsuites are those that are not represented in other other jobgroups.
Tina Muller has created a script to help automate this but this will change also those which should stay intact because "they might be used elsewhere in the future" as she told me.
I tried to run the script to get some idea around it. the script requires to install YAML::LibYAML::API::XS and colordiff package on the workstation. this will let the script do its thing. Although later in the execution you might see some errors about the location of the modules (OpenQA/JobTemplates.pm).
Can't locate OpenQA/JobTemplates.pm in @INC (you may need to install the OpenQA::JobTemplates module) (@INC contains: /usr/bin/../lib /usr/lib/perl5/site_perl/5.30.1/x86_64-linux-thread-multi
/usr/lib/perl5/site_perl/5.30.1 /usr/lib/perl5/vendor_perl/5.30.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.30.1 /usr/lib/perl5/5.30.1/x86_64-linux-thread-multi /usr/lib/perl5/5.30.1 > /usr/lib/perl5/site_perl) at /usr/bin/openqa-validate-yaml line 29.
BEGIN failed--compilation aborted at /usr/bin/openqa-validate-yaml line 29.
the lib issue will be fixed in the next openQA version https://github.com/os-autoinst/openQA/pull/2829. for now a workaround is to use export PERL5LIB=/usr/share/openqa/lib
#5 Updated by ybonatakis about 1 year ago
So what we have to do is to find all the tests' settings in the test suites for each one in the YAST group that are not used in other jobgroups. Then for each of them we need to copy the settings in our YAST yaml(JobGroups/SLE_15_YaST.yaml).
For this we can use the Tina's script.
The question is if we have to do this work for JobGroups/SLE_12_YaST.yaml too(?)
#6 Updated by ybonatakis about 1 year ago
i tried to create a script to compare the yast jobgroup with the rest groups. But i bumped into a small problem with the openqa-python-client(we filed a ticket after discussion on irc). i will continue on Monday trying this or another way to provide a list of those tests that we can reduce
#7 Updated by ybonatakis about 1 year ago
- Status changed from In Progress to Feedback
Comparing with jobgroups in OSD:
i didnt found any that is used by others.
Comparing with TW the following are used by both which if i got it right we cant remove them from the test suite:
[ RAID switch_keyboard_textmode gpt yast2_gui mediacheck crypt_no_lvm remote_ssh_controller RAID0 select_disk installer_extended yast2_nfs_v4_server lvm_thin_provisioning autoyast_multi_btrfs lvm+RAID1 autoyast_gnome yast_no_self_update RAID1 btrfs+warnings RAID10 clone_system yast2_nfs_v3_client yast2_nfs_v4_client cryptlvm remote_vnc_controller nvme autoyast_reinstal autoyast_mini lvm-encrypt-separate-boot modify_existing_partition boot_linuxrc lvm yast2_nfs_v3_server xfs switch_keyboard_gnome yast2_ncurses ]
So the following can be used from the Tina's script for now:
And this list maybe it should be compared with other groups in o3 but
I think it would be nice to have a script or something to find them automatically in the future.
#8 Updated by riafarov about 1 year ago
- Subject changed from [functional][y][Timebox: 16h] Reduce number of test suites used for YaST job group to [functional][y][timeboxed:10h] Reduce number of test suites used for YaST job group
- Due date changed from 2020-03-24 to 2020-04-07
- Status changed from Feedback to Workable
#10 Updated by ybonatakis about 1 year ago
I have generated this list (see attachment) which i hope it can help to do the next step.
In the file, there are 208 combinations of pairs. I "invented" a matching rate for each one.
The calculations made by comparing and matching the key:values of each pair in an additional combination of the remaining matched keys(but not values)
Obviously, the findings are not accurate, in sense that this list provides some trivial investigation but it cannot be completed.
For example: the pair (remote_ssh_target_ftp , remote_vnc_target_nfs) have 0.82 match rate because they have [INSTALLONLY, NETBOOT, NICTYPE, OVS_DEBUG, USE_SUPPORT_SERVER, WORKER_CLASS]. But as i understand, this is a case that we cannot reduce.
In additional the findings can be reduced further because the number of the the combinations is with a pair of two. As an example: RAID pairs can be combined all in one.
#11 Updated by ybonatakis about 1 year ago
I have attached another file which i tried to make groups of test suites, based in the previous list) that contains a set of common variables.
This turned to be harder than i thought so I spent sometime to collect some data to categorize the test_suites per the_most_used variables.
So for the first 10 most common used variables are:
where from them the No1, which shows the value that enables a variable, breaks down to (first 10 elements aagain):
I think from here we can think of a way to group tests more efficient. For example all the test with
#12 Updated by riafarov about 1 year ago
After quick look on the output it's hard for me to understand how to apply it and which test suites can be reduced to one or for which we can move all the settings in the JobGroup, so I guess we will need to spend more time on research.
Also, do you have a script which checks if test suite is enabled in any other job group? As this is very important question we need to answer before acting on any of the test suites.
#13 Updated by ybonatakis about 1 year ago
regarding the first, the answer is yes. i spent the timeboxes towards different directions. If I had more time i would have come up with a combination of the arrays above.
About the script, I made a python script "for all", just to easy some ideas during the investigation. So the answer is something between "there is something" and "need some improvements before get public or be used". I could work on it and provide something that have a more proper output
#15 Updated by riafarov about 1 year ago
- Subject changed from [functional][y][timeboxed:10h] Reduce number of test suites used for YaST job group to [functional][y][epic] Reduce number of test suites used for YaST job group
- Due date deleted (
- Target version changed from Milestone 33 to future
Converting this to epic as we will have multiple subtasks for it.
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html