It's mentioned in an earlier paragraph that Perl bindings in correct version are needed, but there's no note about libvirt even though it should be obvious. So make a clear note on that and while at it, do mention the possibility to get upstream libvirt RPMs from GitLab CI artifacts if users don't feel like building everything on their own. Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx> --- docs/testtck.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/testtck.rst b/docs/testtck.rst index 89760e3f63..f57af61aa8 100644 --- a/docs/testtck.rst +++ b/docs/testtck.rst @@ -73,6 +73,12 @@ Again, for further details on how to update ``lcitool`` virtual machines, please refer to `Updating VMs with a given project dependencies <https://gitlab.com/libvirt/libvirt-ci/-/blob/master/docs/vms.rst>`__ +Note that lcitool only installs build dependencies, so as mentioned above you'll +need both libvirt **and** libvirt Perl bindings installed in order to be able +to run TCK. You can (depending on use case) either build both inside the VM and +install manually or install the corresponding RPMs from GitLab CI build +artifacts. + We also recommend executing TCK using the Avocado framework as the test harness engine which means that you'll have to install Avocado in the test environment as well. You can get it either from -- 2.41.0
