mirror of
https://github.com/systemd/systemd.git
synced 2026-11-07 13:57:10 +00:00
Zbigniew Jędrzejewski-Szmek
8bd025111c
In general, "unit tests" are better then "integration tests" which require an image to be created. For stuff that can be immediately tested from the build directory, let's use unit tests. The subtest ran inside the TEST-74 image and looked the programs up by a hard-coded list of names. Register it with meson instead, so that it runs in "meson test" against the freshly built binaries, using the actual list of installed programs and aliases. A few programs cannot be introspected: ukify is (still) a Python script, the mount helpers implement the mount(8) interface, and systemd does not list its init alias among its names. Aliases are passed as the bare names of the symlinks in the build directory, so the script turns them into paths before running them, and checks the invoked name against all names of a command, as the aliases of a command are listed after its main name. The introspection of each program is captured once and inspected with jq several times, which keeps the test at a few seconds. The script is not installed, since the installed unit tests are run without arguments. jq is added to the dependencies of the GitHub unit test job.