When tests fail, as they often will, the debugger can greatly shorten the time it takes to figure out why. The Kubevirt functional tests run essentially as a remote client. Getting a debuggable setup is not that different from my earlier post on running virt-launcher in the debugger.
I started by trying to run the unit tests list other tests, but had a similar problem to the virt-controller setup. Looking at cluster/run_tests.sh what is not clear is that it is doing a directory based run of the tests. Changing the config to look like this worked:
Note that I changes Kind to directory and edited the Directory field to point to where we have our unit tests. The program arguments field. looks like this in full: