As mentioned in test/CMakeLists.txt: # These are not so much "tests" as "small example programs". They illustrate # how to use the library, how to perform common tasks. For example, test/testexternalcommand.cpp can't even execute a command, the result (shown in the log if we force return 1) is: > "Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory" And there doesn't seem to be a solution right now: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3648 So I suggest creating openQA tests for the openSUSE KDE test suite (https://en.opensuse.org/openSUSE:OpenQA/Partners#GNOME_&_KDE). These tests should at least create a partition, resize it, move it and remove it. And repeat these actions with various file systems (ideally all of them).
Yes, openQA could be useful. As for testexternalcommand.cpp, it works here, so something is missing on your test system, the error message suggest that dbus is not running (to execute external command test program needs to obtain authorization from polkit).
Yes, it works fine in appearance, but if we force it to fail by returning 1 (https://invent.kde.org/tbertels/kpmcore/-/commit/ddc53ff9582bc458b8341ec614ec06baf98d8535) we realize that it's not really doing much: https://invent.kde.org/tbertels/kpmcore/-/jobs/2164831