action #42578
Updated by okurz almost 6 years ago
****See See motivation in the parent ticket. After discussion regarding #42227, we recognized that we are not clear what is the purpose of the test suite, as some parts are covered in other scenarios. So there are 2 options: a) Purpose is to create image for further tests Then installation is not the most efficient way to do that as well. Then we keep them in current job group. b) Purpose is to test installation and use resulting image for further testing In this case Y-subteam should take over to keep test suite in a good shape and produce images ## Acceptance criteria * **AC1:** 1. Decision is defined, accepted by all stakeholders and documented for create_hdd* scenarios ## Suggestions * Discuss within the QSF-y team, then QSF, then ask some stakeholders outside QSF for their opinion and requirements, e.g. RMs, *or* just go with any decision when you see the impact not too big and assume "silent consent" based on this ticket's content * Document the results, e.g. in this ticket * Ensure the test suite descriptions reflect the common understanding * If trivial, adjust test suites on mismatch *or* create follow-up tasks