remember, though, this may come under the whole 'do testing in anaconda CI instead' thing. We should check with @jkonecny .

hi looks like a good idea, @kkoukiou you know better than me how problematic or if we already have something like that?

Yes @lruzicka this is covered upstream now, https://github.com/rhinstaller/anaconda-webui/blob/8c722eac9ff1c512dd99383ff2c7361ba6b8aedc/test/check-storage-cockpit-e2e#L120

I added this to the mapping that reports our results to your test pages: https://github.com/rhinstaller/anaconda-webui/pull/779/commits/fe5e9880416724debcdef008bf25a2201c263e94

I would suggest that we focus on increasing the mapping and possibly the coverage upstream, and test in openQA scenarios which we can't test upstream (live image specific scenarios, ex: keyboard configuration)
We also still haven't implemented multi arch testing.

I would also say that to make this really viable we need to fix the triggering so the upstream tests reliably run on at least:

• All release candidate composes
• All nightly composes for which validation events are created

For openQA we simply run on any compose that contains testable images. But I don't care exactly how it's done for the upstream anaconda CI as long as it covers that list.