On 16/07/2024 20.03, Paolo Bonzini wrote:
Il mar 16 lug 2024, 18:45 John Snow <js...@redhat.com
<mailto:js...@redhat.com>> ha scritto:
My only ask is that we keep the tests running in the custom venv
environment we set up at build time
Yes, they do, however pytest should also be added to pythondeps.toml if we
go this way.
If we move to pytest, it's possible we can eliminate that funkiness,
which would be a win.
There is the pycotap dependency to produce TAP from pytest, but that's
probably something small enough to be vendored.
The next version is only depending on pycotap now. I'm installing it in the
venv there that we also install when running the old avocado tests. Not sure
whether that's the best solution, though. Would it be OK to have it in
python/wheels/ instead?
And also it depends on what
the dependencies would be for the assets framework.
>
I'm also not so sure about recreating all of the framework that pulls vm
images on demand, that sounds like it'd be a lot of work, but maybe I'm
wrong about that.
Yep, that's the part that I am a bit more doubtful about.
As I'm mentioned elsewhere, the tests that really have a hard dependency on
the Avocado framework are only the tests that use the cloud-init images via
the LinuxTest class. That's currently onle these files:
- boot_linux.py
- hotplug_blk.py
- hotplug_cpu.py
- intel_iommu.py
- replay_linux.py
- smmu.py
I assume we could continue using avocado.utils for the cloud-init stuff
there, and just run them via the meson test runner, too. I'll give it a try
when I get some spare time.
Thomas
