From: Eduardo Habkost <ehabkost@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: cohuck@redhat.com, f4bug@amsat.org, qemu-devel@nongnu.org,
Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
amarkovic@wavecomp.com, crosa@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] tests/acceptance: Update MIPS Malta ssh test
Date: Wed, 21 Aug 2019 18:00:30 -0300 [thread overview]
Message-ID: <20190821210030.GH7077@habkost.net> (raw)
In-Reply-To: <CAL1e-=hWc6G7Ob+LU7EWoY3LVBvABY2ky=RT28dSzqM=9O=OEA@mail.gmail.com>
On Wed, Aug 21, 2019 at 10:27:11PM +0200, Aleksandar Markovic wrote:
> 02.08.2019. 17.37, "Aleksandar Markovic" <aleksandar.markovic@rt-rk.com> је
> написао/ла:
> >
> > From: Aleksandar Markovic <amarkovic@wavecomp.com>
> >
> > This little series improves linux_ssh_mips_malta.py, both in the sense
> > of code organization and in the sense of quantity of executed tests.
> >
>
> Hello, all.
>
> I am going to send a new version in few days, and I have a question for
> test team:
>
> Currently, the outcome of the script execition is either PASS:1 FAIL:0 or
> PASS:0 FAIL:1. But the test actually consists of several subtests. Is there
> any way that this single Python script considers these subtests as separate
> tests (test cases), reporting something like PASS:12 FAIL:7? If yes, what
> would be the best way to achieve that?
If you are talking about each test_*() method, they are already
treated like separate tests. If you mean treating each
ssh_command_output_contains() call as a separate test, this might
be difficult.
Cleber, is there something already available in the Avocado API
that would help us report more fine-grained results inside each
test case?
>
> Thanks in advance,
> Aleksandar
>
> > Aleksandar Markovic (2):
> > tests/acceptance: Refactor and improve reporting in
> > linux_ssh_mips_malta.py
> > tests/acceptance: Add new test cases in linux_ssh_mips_malta.py
> >
> > tests/acceptance/linux_ssh_mips_malta.py | 81
> ++++++++++++++++++++++++++------
> > 1 file changed, 66 insertions(+), 15 deletions(-)
> >
> > --
> > 2.7.4
> >
> >
--
Eduardo
next prev parent reply other threads:[~2019-08-21 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 15:35 [Qemu-devel] [PATCH 0/2] tests/acceptance: Update MIPS Malta ssh test Aleksandar Markovic
2019-08-02 15:35 ` [Qemu-devel] [PATCH 1/2] tests/acceptance: Refactor and improve reporting in linux_ssh_mips_malta.py Aleksandar Markovic
2019-08-02 15:58 ` Philippe Mathieu-Daudé
2019-08-28 20:58 ` Cleber Rosa
2019-08-02 15:35 ` [Qemu-devel] [PATCH 2/2] tests/acceptance: Add new test cases " Aleksandar Markovic
2019-08-28 21:27 ` Cleber Rosa
2019-08-21 20:27 ` [Qemu-devel] [PATCH 0/2] tests/acceptance: Update MIPS Malta ssh test Aleksandar Markovic
2019-08-21 21:00 ` Eduardo Habkost [this message]
2019-08-22 3:15 ` Aleksandar Markovic
2019-08-22 17:59 ` Aleksandar Markovic
2019-08-26 19:52 ` Aleksandar Markovic
2019-08-28 21:24 ` Cleber Rosa
2019-08-29 18:20 ` Aleksandar Markovic
2019-08-29 17:55 ` Eduardo Habkost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190821210030.GH7077@habkost.net \
--to=ehabkost@redhat.com \
--cc=aleksandar.m.mail@gmail.com \
--cc=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=cohuck@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).