QA (public) » openQA Project (public) » openQA Tests (public)

I've dumped sle 12 sp3 functional job group, replaced sle-12-sp3 settings with sle-15. Some of the repos do not exist yet, e.g. aytest_repo (http://download.suse.de/ibs/Devel:/YaST:/SLE-15/SLE_15/)
I believe second alternative fits best, as I expect that most of test suites will need tuning. Also, we will have list of jobs to be moved to sle 15 functional group, meaning chances that we miss something are low even without script. Once job group has test suites, all changes that are applied to sle 12 sp3 have to be verified with sle 15.
Please, find suggested json in the attachment.

Attached json file was used to create job templates.

Discussed with PO maritawerner and TL sebchlad: As full proxy-SCC enablement will take some more time we already started now to copy over the full SLE functional test matrix to its according job group to check which scenarios we can already fix, e.g. when they are relying only on the installation workflow. ~1 person will care about the review and fixing of existing failures as well as workarounds to provide prerequisities for other QA groups and other job groups than "Functional" within openQA based on available media which are not intended to be shipped to customers, e.g. the "Server"-medium as well as the module media. Either LeanOS can be extended with these media (and according repositories) or we have to revert to the full Server-DVD and add media to that to provide prerequisities for further testing. I estimated this to take about 2-4 weeks to have a complete coverage of all what we had for SLE 12 SP3. Within 2-10 days we should be able to provide an image corresponding to "create_hdd_minimal_base+sdk" which should enable further testing in other job groups based on that, e.g. kernel testing based on LTP as a first step. Other members of the Functional team will focus on existing tasks be it fixing known issues, enhancement to existing tests or new tests based on already existing requests. If necessary the ressource application can be adjusted in both directions, e.g. more or less effort on SLE15 workaround implementation. Other teams should not be blocked as there are still enough tasks to be done, e.g. for stabilization or openSUSE related.

due to changes in a related task

due to changes in a related task

discussed status in M10 review, blocked by subtasks

We missed the chance to talk f2f. And yes, we could just query for "[sle][functional][sle15]" instead but this ticket also shows our initial plan of what we wanted to do and we have subtickets now which were in most cases observations on what needs to be adapted for sle15 from the start already. IMHO it's good to have this ticket to show what was already known that we need to adapt for sle15 but did not yet accomplish. I will check that next week then.

updated open tasks.

The subtickets #23452, #23454 should be done first before we can close here.

Reviewed the current test coverage again. Seems like we have no scenario still there which does not seem to make any sense at all. Updated subtickets and removed the connection for some siblings. All tasks in the description except for the optional one considered done.