coordination #88684

coordination #64126: [qe-core][epic] Identify packages that have automated indirect testing or that have sufficient build time test suite

[qe-core][epic][qem] Identify packages that we are indirectly testing

Added by tjyrinki_suse over 2 years ago. Updated 3 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


We test some packages indirectly as part of other packages' test. The template generator ( Update Squad uses does not detect these cases, and does not then tell the update tester there's automatic openQA regression testing.

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 tests webkit to an enough extent, webkit could be marked as automatically regression tested, and manual testing would no longer be required.

Acceptance Criteria

AC1: Identify what packages we are regression testing indirectly, and via which tests, check if it's "sufficient" for regression testing of that package: sufficient means at least similar level as in manual testing done in case of updates, see database for how the packages was teded manually.
AC2: Mark sufficiently indirectly regression tested packages 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.


#1 Updated by tjyrinki_suse over 2 years ago

  • Description updated (diff)

#2 Updated by tjyrinki_suse about 2 years ago

  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by tjyrinki_suse over 1 year ago

  • Description updated (diff)

Changed "decide" -> "check" in AC1. GTK was offered as an example of something that is being tested indirectly, yet not documented at - however in this example there is only about 1 GTK update per year (

#4 Updated by apappas over 1 year ago

  • Assignee set to apappas

#5 Updated by apappas over 1 year ago

  • Status changed from Workable to Feedback

Notes from the refinement meeting:

  1. It is not the role of the team members to decide what constitutes "enough" testing. If there is a ticket whose ACs can be fullfiled by existing tests we can certainly tell you that, but first we need to know what they are.
  2. The update validation team should be asked which are the packages that still have non-automated time consuming tests, and we should focus on them.

#6 Updated by tjyrinki_suse over 1 year ago

  • Tracker changed from action to coordination
  • Subject changed from [qe-core][qem] Identify packages that we are indirectly testing to [qe-core][epic][qem] Identify packages that we are indirectly testing
  • Assignee deleted (apappas)
  1. The AC1 defines the "enough" testing, ie comparing how manual testing was done. If similar level of testing is done indirectly already in openQA, it's enough.
  2. This is a good idea, to ask if they have ideas.

All in all this is more an epic that cannot be fully considered "done" by any single group of tasks.

Also available in: Atom PDF