From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Suggestion to use python-parameterized for QA
Date: Mon, 15 Nov 2021 21:26:41 +0100 [thread overview]
Message-ID: <7f35ae7d-d12b-8ba3-5459-c2fb92f3f38f@gmail.com> (raw)
In-Reply-To: <CANNYZj-UTWzhnRoxTpTn3kqp4d7FiRk0NPD_Mon0cOd6Js13UQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
It's substituted further down into
def test_sbin_init(self, _, origInit):
parameterized.expand generates two tests out of it. The string parameter
is used as a suffix for the test, the rest is used as input parameters,
i.e. the first test would be called with origInit=True, the second one
with origInit=False.
The sample output looks like this:
2021-11-15 20:21:15,740 - oe-selftest - INFO - RESULTS -
overlayfs.OverlayFSEtcRunTimeTests.test_sbin_init_0_original: PASSED
(295.73s)
2021-11-15 20:21:15,740 - oe-selftest - INFO - RESULTS -
overlayfs.OverlayFSEtcRunTimeTests.test_sbin_init_1_preinit: PASSED
(177.97s)
Vyacheslav
On 15.11.2021 21:20, Alexander Kanavin wrote:
> I can't understand what is supposed to happen, perhaps because it's
> incomplete? There's
>
> @parameterized.expand([
>
> ("original", True),
>
> ("preinit", False),
>
> ])
>
> but where is that used?
>
> Alex
>
[-- Attachment #2: Type: text/html, Size: 4189 bytes --]
next prev parent reply other threads:[~2021-11-15 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 19:34 Suggestion to use python-parameterized for QA Vyacheslav Yurkov
2021-11-15 19:38 ` [OE-core] " Alexander Kanavin
2021-11-15 19:53 ` Vyacheslav Yurkov
2021-11-15 20:20 ` Alexander Kanavin
2021-11-15 20:26 ` Vyacheslav Yurkov [this message]
2021-11-15 20:56 ` Alexander Kanavin
2021-11-16 6:16 ` Vyacheslav Yurkov
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=7f35ae7d-d12b-8ba3-5459-c2fb92f3f38f@gmail.com \
--to=uvv.mail@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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