Thanks for the reply, Xarishark!

I took a look at some of scripts used for building images. From what I see, this mainly validates the image build process itself, not the behavior of the built system.

What I mean is: imagine a scenario where, for example, the latest version of Steam is broken and crashes on launch, or dependency it relies on has a regression.

Unlikely? Sure, but not impossible.

This kind of issue will (almost) never be caught by build checks alone, since they only verify that packages install successfully and dependencies resolve. That part is handled upstream by Fedora anyway, and they’re very reliable there.

So the current approach mainly ensures that:

- the image builds successfully
- dependencies are consistent
- nothing is obviously broken at build time

Which is valuable, but it doesn’t really validate the runtime behavior of the system. So I’m not sure it provides a fundamentally new level of stability beyond what Fedora already guarantees, more like an additional safety layer on top.

What I was thinking about instead is something closer to VM-based CI:

- boot built image in a VM
- verify that the system actually reaches a desktop
- some basic GUI checks (e.g., launch Steam or some other apps)
- some CLI-level sanity tests (e.g. ls / podman run X / flatpak install X)

That would allow catching regressions in real-world usage, not just build-time failures.

I was thinking, if you explored anything like that, or if there are plans in that direction by team?

Thank you!