On Fri, Jul 2, 2021 at 7:48 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
On Thu, Jul 01, 2021 at 06:09:47PM -0300, Beraldo Leal wrote:
On Thu, Jul 01, 2021 at 07:04:32PM +0100, Daniel P. Berrangé wrote:
On Wed, Jun 30, 2021 at 01:36:30PM -0300, Beraldo Leal wrote:
If I look at Avocado, I think (correct me if i'm wrong)
1. The harness is essentially the standard Python harness with a thin CLI wrapper. Thus needs all tests to implement the Python test APIs 2. The support infra is all custom APIs using libvirt-python 3. The tests are to be written entirely in Python, to integrate with the python test harness
This is supported already:
$ avocado run --tap - --test-runner='nrunner' tests/domain/transient.py 1..3 ok 1 tests/domain/transient.py:TransientDomain.test_autostart ok 2 tests/domain/transient.py:TransientDomain.test_lifecycle ok 3 tests/domain/transient.py:TransientDomain.test_convert_transient_to_persistent
BTW, where are you getting 'avocado' from ? AFAICT, it still is not made available in Fedora repositories - I found a copr repo only. It will need to graduate into official Fedora repositories before we can depend on it really.
Hi Daniel, It has been in Fedora for a long time. But, during the modularization effort, it became part of the "avocado" module. Now, we're bringing back the non-modular packages. For now: $ dnf module enable avocado:latest $ dnf module install avocado:latest Should work. Thanks, - Cleber.
Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|