QA » openQA Project » openQA Tests

Will handle SLE15SP5/TW with textmode at first.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16722

We can re-use the autoyast configuration files.

As discussed with Santiago, Yast team has done a lot of work on autoyast_create_hdd_textmode*.

But they may have some other testing purpose to publish the qcow2 images for libyui tests later.

I would suggest if QE-CORE and Yast team can work together for this task.

We can create a basic qcow2 image at first via autoyast and then we can create images for libyui test based on this one.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16755
This PR has removed some non-default installed packages in autoyast configuration file.

Now create_hdd_textmode_autoyast tests are passed on both SLE15SP5 and TW:
TW
SLE

SPVM test is failed due to infra issue

Create_hdd_gnome_autoyast
are covered by QE-YaST team. Do we need to take them back?
@szarate

Private tests are done, let me try to add the tests to job groups (both O3 and OSD)
OSD name - > create_hdd_textmode_autoyast
O3 name - > create_hdd_textmode_autoyast

There should be at least one non-autoyast installation, there were yast bugs which didn't show up in auotyast installation.
I can't say what test should be left as non-autoyast installation, I guess it can be qam-gnome, there are not big differences between installation except patterns.

dzedro wrote:

There should be at least one non-autoyast installation, there were yast bugs which didn't show up in auotyast installation.
I can't say what test should be left as non-autoyast installation, I guess it can be qam-gnome, there are not big differences between installation except patterns.

Thanks much! it makes sense.

For products in development phase [sle15sp5/TW], I will keep both interactive installation and autoyast ones to make sure we don't lose coverage.

For QEM, I agree with you. I will keep some jobs which don't have dependency.