Waiting for the usrmerge patchset to trickle down back to us in openembedded-core.

Krisztian, is it there any current or planned sanity test for this feature? How would you recommend that we test its functionality?

There is a very basic sanity test which simply checks if the minimum set of files necessary for flatpak 3rd-party application support are present in the image.

It's added by this commit: https://github.com/klihub/meta-flatpak/commit/82084a040ae33eb21792d24dc5831d1487715d9c

The test lives together with the rest of the flatpak support code in meta-flatpak.

Are you talking about automatic testing during bitbake, or about manual testing ?

In automatic testing a few additional things could be verified, for instance if there are pre-declared 3rd-party repositories whether the necessary data for those end up correctly in the image, and taken into use by the daemon that automatically polls flatpak remotes for updates. See the comment about FLATPAK_APP_REPOS, flatpak-passwd and flatpak-group in https://github.com/klihub/meta-flatpak/blob/intel-iot-refkit/flatpak/classes/flatpak-variables.bbclass.

There are other tests possible but they require much more complex setups. For instance automatic installation and startup of flatpak applications could be automatically tested but it requires:

- pre-declaring a test app repo,
- creating the test repo
- publishing/exposing the test repo iver HTTP to clients,
- building flatpak applications against the generated flatpak-sdk runtime
- publishing those in the pre-declared repo
- booting up an image built with the pre-declared repos
- checking if the test applications from the repository ended up pulled in and started in the image

All of these could be technically automated. It just depends on your test environment and its limitations how difficult/horrendously laborous that ends up to be.

Thanks Krisztian. I've updated QA bug 11202 according to your comments.