This is a request from the anaconda devs. Ref https://bugzilla.redhat.com/show_bug.cgi?id=2238045 . There's an interactive flow in anaconda when a kickstart-driven install lists a package that doesn't exist, which had a bug. The anaconda team would like us to test that in openQA (it does seem like a natural fit). So the test would run an install with a kickstart that intentionally listed a missing package, and check that the expected UI flow appeared and could be successfully clicked through to complete the install.
@jkonecny sorry, just wanted to check on this - we didn't get to this yet, and I know you have more testing in your CI now; is this something you've covered with upstream tests or would it still be useful in openQA? thanks!
Metadata Update from @adamwill: - Custom field story_points adjusted to 2
Right now I don't think we have anything that could do this with our current upstream CI toolinng - we have some kickstart tests, but those only check a %packages section flag that makes Anaconda ignore those missing packages. We simply don't have anything to click thorough those warnings & finish the installation. I think OpenQA could certainly do this & is the only short term solution if we wanted to have this flow covered. But longer term I wonder if perhaps the Web UI tests could handle this ? Quite a few things would have to be implemented first though - proper support for kickstart install and RPM based installation in the Web UI and possibly also some added support for combining kickstarts & Web UI based tests in the tooling.
Also CC @kkoukiou to keep you the picture. :)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/os-autoinst-distri-fedora/issues/336
Please continue any further discussion there.