From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Yeoh Ee Peng <ee.peng.yeoh@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oe-selftest: runqemu: add tests for qemu boot and shutdown
Date: Mon, 9 Apr 2018 15:34:18 +0300 [thread overview]
Message-ID: <12143047-5587-0874-4cdf-6989cab74b27@linux.intel.com> (raw)
In-Reply-To: <1523244763-108834-1-git-send-email-ee.peng.yeoh@intel.com>
On 04/09/2018 06:32 AM, Yeoh Ee Peng wrote:
> QA team were testing qemu boot image and shutdown on each
> qemu architecture manually. Add automated test to test qemu boot on
> ext4 and nfs, finally check that it can shutdown properly.
>
> Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com>
> ---
> meta/lib/oeqa/selftest/cases/runqemu.py | 61 +++++++++++++++++++++++++++++++--
> 1 file changed, 59 insertions(+), 2 deletions(-)
>
> diff --git a/meta/lib/oeqa/selftest/cases/runqemu.py b/meta/lib/oeqa/selftest/cases/runqemu.py
> index 47d41f5..7288ab2 100644
> --- a/meta/lib/oeqa/selftest/cases/runqemu.py
> +++ b/meta/lib/oeqa/selftest/cases/runqemu.py
> @@ -3,9 +3,10 @@
> #
>
> import re
> -
> +import tempfile
> +import time
> from oeqa.selftest.case import OESelftestTestCase
> -from oeqa.utils.commands import bitbake, runqemu, get_bb_var
> +from oeqa.utils.commands import bitbake, runqemu, get_bb_var, runCmd
> from oeqa.core.decorator.oeid import OETestID
>
> class RunqemuTests(OESelftestTestCase):
> @@ -136,3 +137,59 @@ SYSLINUX_TIMEOUT = "10"
> cmd = "%s %s" % (self.cmd_common, rootfs)
> with runqemu(self.recipe, ssh=False, launch_cmd=cmd) as qemu:
> self.assertTrue(qemu.runner.logged, "Failed: %s" % cmd)
> +
> +class QemuTest(OESelftestTestCase):
Please add comments that explain the need for a separate class, what the
two classes do and how they differ.
Alex
next prev parent reply other threads:[~2018-04-09 12:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 3:32 [PATCH] oe-selftest: runqemu: add tests for qemu boot and shutdown Yeoh Ee Peng
2018-04-09 12:34 ` Alexander Kanavin [this message]
2018-04-10 0:57 ` Yeoh, Ee Peng
-- strict thread matches above, loose matches on Subject: below --
2018-04-09 17:43 Yeoh Ee Peng
2018-04-10 1:01 ` Yeoh, Ee Peng
2018-04-10 7:00 ` Anuj Mittal
2018-04-10 7:24 ` Yeoh, Ee Peng
2018-04-10 7:29 ` Alexander Kanavin
2018-04-10 7:39 ` Yeoh, Ee Peng
2018-04-10 9:41 ` Richard Purdie
2018-04-10 10:01 ` Yeoh, Ee Peng
2018-04-10 1:28 Yeoh Ee Peng
2018-04-20 7:15 ` Richard Purdie
2018-04-20 8:27 ` Yeoh, Ee Peng
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=12143047-5587-0874-4cdf-6989cab74b27@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=ee.peng.yeoh@intel.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