On Sun, Oct 9, 2022 at 10:51 AM Ani Sinha <a...@anisinha.ca> wrote:
>
> On Wed, Sep 28, 2022 at 1:14 PM Thomas Huth <th...@redhat.com> wrote:
> >
> >
> > > Do not do any of this stuff, it is irrelevant to QEMU's needs.
> > > A developer using Avocado with QEMU does nothing more than:
> > >
> > > make check-avocado
> >
> > Right. And if you want to run individual tests, you can also do it like
> > this:
> >
> > make check-venv # Only for the first time
> > ./tests/venv/bin/avocado run tests/avocado/boot_linux.py
>
> Ok this seems to work after I did a pip3 install of avocado in the host.
>
> ./tests/venv/bin/avocado run tests/avocado/version.py
> JOB ID : 8dd90b1cb5baf3780cc764ca4a1ae838374a0a5f
> JOB LOG :
> /home/anisinha/avocado/job-results/job-2022-10-09T10.48-8dd90b1/job.log
> (1/1) tests/avocado/version.py:Version.test_qmp_human_info_version:
> PASS (0.04 s)
> RESULTS : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0
> | CANCEL 0
> JOB TIME : 3.51 s
>
> I see that the output is not tap compliant like the qtests tests are.
> how do I choose tap?
>
> ./tests/venv/bin/avocado-runner-tap --help
> usage: avocado-runner-tap [-h]
> {capabilities,runnable-run,runnable-run-recipe,task-run,task-run-recipe}
> ...
>
> nrunner application for executable tests that produce TAP
>
> positional arguments:
> {capabilities,runnable-run,runnable-run-recipe,task-run,task-run-recipe}
> capabilities Outputs capabilities, including runnables and commands
> runnable-run Runs a runnable definition from arguments
> runnable-run-recipe
> Runs a runnable definition from a recipe
> task-run Runs a task from arguments
> task-run-recipe Runs a task from a recipe
>
> options:
> -h, --help show this help message and exit
>
Never mind
$ ./tests/venv/bin/avocado run tests/avocado/version.py --tap -
1..1
ok 1 tests/avocado/version.py:Version.test_qmp_human_info_version
from https://avocado-framework.readthedocs.io/en/52.0/ResultFormats.html .
