coordination #88684

Updated by tjyrinki_suse over 2 years ago

We test some The first part would be to identify what packages we are actually regression testing indirectly in some tests and decide if it's sufficient or not, and eventually mark them as part of automated (for example an empty entry at PES wiki with a command). Go through existing tests and decide what else is being used there, or the other packages' test. The template generator ( Update Squad uses does not detect these cases, way around take a specific package and does not then tell the update tester there's automatic openQA regression testing. look for where it is used. 

 For example, webkit is used in evolution - if there have been maintenance updates of webkit, was the manual testing more complex than what the evolution automatic test case would be, or not? If the evolution test evolution, so it might be enough to check those tests webkit to an enough extent, webkit could be marked as automatically regression tested, and manual testing would there is probably no longer be required. need for additional resources and test. 

 ## Acceptance Criteria (the above part of description modified from Juraj Hura's idea) 

 AC1: Identify what packages we are regression testing indirectly, The current machine readable data for automation is at and via which tests, decide if it's "sufficient" so that should be appended - probably with new sections for regression testing of that package. Sufficient means similar indirect and build time ones - as in manual testing done in case of updates, see database for how the needed with packages was teded manually. 
 AC2: Mark sufficiently indirectly regression tested packages that would be now marked as automatically tested. This can be done, in the current way, with an entry at PES wiki page ( - the template generator parses that page to know if there has been automatic regression testing. Add a separate header for indirectly tested packages.