Project

General

Profile

Actions

coordination #104829

closed

[Epic] Improve schedules for test suite in YaST group

Added by JERiveraMoya over 2 years ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
Start date:
2022-01-12
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

We want to have a better idea about how to create some mechanism (perhaps and enhanced scheduler) to share the common parts in the schedules (reducing number of existing files and content on those).

Test suites contains test module scheduled that are not unique of those test suite, they are there due to bugs, mistakes, hidden logic, convenience and all of that makes very difficult to find some sort of common denominator, in other words, what is shared with other test suite and what is not and it is unique of that particular test suite.

We can always create the default test suite without taking account those parts that are branched/unique, but likely the default installation it is not an specific test suite and more like a template where some parts are unavoidable to be changed depending on the specific env where they run. Also we don't want to end up with many-many default specific yaml files. So create the default installation + repeating parts is something useful at the moment and in the same side, instead of being creating 11 files for the aprox 11 flavors (arch + virtualization) that we have.

AC1: Figure out what is unique on each test suite, for example, remove inconsistencies like not needed tests modules.
As it is a big scope, we could do it per architecture first and then per test suite (in parallel and horizontal as we use to call it, as we previously did with our effor applying libyui-rest-api)

AC2: Create new test suite which will be a default installation + those repetitions found or add those repetitions to extended test suite and even consider to create more extended test suites.


Subtasks 9 (0 open9 closed)

action #104832: Unschedule updload_assets and remove test_data where not neededClosedJRivrain2022-01-12

Actions
action #104845: Remove test module `hostname_inst`where not needed and not perform full installation where neededClosedrainerkoenig2022-01-12

Actions
action #104850: Unschedule isosize from all test suite except installer_extendedClosedoorlov2022-01-12

Actions
action #105043: Create PoC for YAML schedule with initial ideasClosedJERiveraMoya2022-01-19

Actions
action #106847: Migrate a few more YAML schedules using PoC for enhanced scheduler Resolvedrainerkoenig2022-02-15

Actions
action #110236: Create unit test for YAML schedule with reusable flowsResolvedrainerkoenig2022-04-25

Actions
action #110239: Create script to generate list of test modules scheduled by YAML schedule when using default/flows files.Resolvedrainerkoenig2022-04-25

Actions
action #110242: Add CI check in gitlab to ensure default and flows YAML files existResolvedamanzini2022-04-25

Actions
action #110245: Document new feature in YAML schedule with default and flowsResolvedhjluo2022-04-25

Actions
Actions #1

Updated by JERiveraMoya over 2 years ago

  • Priority changed from Normal to High
Actions #2

Updated by JERiveraMoya over 2 years ago

  • Priority changed from High to Normal
Actions #3

Updated by JERiveraMoya over 2 years ago

  • Description updated (diff)
Actions #4

Updated by JERiveraMoya over 2 years ago

  • Subject changed from Improve schedules for test suite in YaST group to [epic] Improve schedules for test suite in YaST group
Actions #5

Updated by JERiveraMoya over 2 years ago

  • Subject changed from [epic] Improve schedules for test suite in YaST group to [Epic] Improve schedules for test suite in YaST group
Actions #6

Updated by JERiveraMoya over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #7

Updated by JERiveraMoya 4 months ago

  • Status changed from Workable to Resolved
Actions

Also available in: Atom PDF