coordination #104829
Updated by JERiveraMoya over 2 years ago
#### 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. found.