Hi @FengYang,
My usage scenario is to have a minimal guest/host without a compiler installed. Even when downloading JeOS from the location specified in shared/downloads/jeos-19-64.ini, the system seems to lack a compiler. It is important for us to test a system that looks as much as possible as what our customers will be running in the field, and those systems almost always lack a build environment.

About checking the existence of the tools: My thinking was that since /tmp is used, its probably flushed during a reboot and that we could assert that the tool available there is the correct version. But if we can't, I'll rewrite the patch to not do this check.

The TC gets more complex, yes. Perhaps another way forward would be to abstract the copying and building of the test binaries to a separate class?

Thanks,
/Jonas